WAP200 remote managment

[mrssec323]

Hi,

I do have problems with remote management of a Wireless Accespoint WAP200.

The WAP200 is connected to a router RVS4000 and works well.

There are several nodes in the LAN, all static IP, all forwarded in the RVS4000.

All nodes can be managed in the LAN as well as from outside.

Exept the WAP200, from inside in LAN no problem, but from outside gives a 404 return.

I build other similar LAN's, but the same, no connection.

What goes wrong? please help.

[vwooten]

Hello mrssec323,

What do you mean by "...from outside gives a 404 return." Are you trying to access the WAP200 from a remote location such as your home or a hotel or are you trying to access it from outside of the building via wireless?

If you are trying to access it from a remote location, what ports are you forwarding? Do you have Web HTTPS Access enabled? Are you contacting the device from the public ip address or through a VPN connection?

Regards,

-Van

[David Hornstein]

Hi Van,

What do you think of the following, it's worth a check..

First thing i thought of was, ok mrssec323 seems to know how to do a port forward  from his WAN to LAN hosts from his RVS4000,  because he commented "All nodes can be managed in the LAN as well as from outside."

But he mentions he statically defines the IP addresses of Hosts on the LAN.   I am wondering if it is as;

1.  something simple as having the wrong default gateway address programmed in on the WAP200 ?

2.  or the wrong port forward on the RVS4000.

regards Dave

[vwooten]

Hi David,

It is possible that it could be a default gateway configuration on the WAP200. However, I think we need some more information on how mrssec323 is trying to access the WAP200 specifically.

     Mrssec323 does say,

     "There are several nodes in the LAN, all static IP, all forwarded in the RVS4000. All nodes can be      managed in the LAN as well as from outside."

I am just wondering which port he is trying to forward for the WAP200 and if that port has been forwarded twice. It could be a problem with the port translation on the RVS4000.

Regards,

-Van

[mrssec323]

Hallo Van and Dave,

Thanks for response. I will give you more info, see table.

Contacting the WAP200 from outside, means remote from anywhere in the internet and is not possible.

	RVS4000	WAP200	Cam WVC54GCA
WAN	82.151.x.x	n/a	n/a
LAN	192.168.1.201	192.168.1.202	192.168.1.11
Gateway	82.151.y.y	192.168.1.201	192.168.1.201
DNS 1/2	82.151.32.35/36	82.151.32.35/36	82.151.32.35/36
Subnet	255.255.255.0	255.255.255.0	255.255.255.0
Port single fw AP	3004-tcp-192.168.1.202	n/a	n/a
Port single fw Cam	3001-tcp-192.168.1.11	n/a	n/a
AP mode	n/a	Access Point	n/a
Firmware	1.3.3.5	n/a	v1.1.01 build 01
Hardware Ver.	n/a	1.0	n/a
Softw. Ver.	n/a	2.0.2.4-ETSI	n/a
VPN	no	no	no
HTTPS Web Enabled	no	no	no
Contacting via Int.	OK	not OK	OK
Contacting via LAN	OK	OK	OK

[vwooten]

Hello mrssec323,

I see that the port forwarded for the WAP200 is 3004-tcp. Is 3004 the internal and external port forwarded to the WAP200? If so, then you may want to try using 3004 for the external port and 80 for the internal port.

Regards,

-Van

[mrssec323]

Hello Van Wooten,

I just solved the problem, changed port forwarding to 443.

Port 443 is the right one for the WAP200 (port 80 does not work)

I came to it by observing making connection to the WAP200 in the LAN. At the log-on screen you see port 443.

Good lesson for henceforth closer look.

Thanks to all.

Regards. 

[David Hornstein]

Hi

So you had previously enabled or selected the option for Web HTTPS Access:

Now it makes sense, the manual does state ;"

Web Access

To increase the security on accessing the web-based utility, you can enable HTTPS. Once enabled, users need to use https://    when accessing the web-based utility. 

good that you resolved your issue.

regards Dave

[mrssec323]

Hi,

The problem was not caused by using http or https.

Only using the right port.

Thanks anyway

regards MrsSec