The server can’t see its websites behind the Ruckus VF2825. Is this by design? I can get to the website from another provider.

I can see the website from another network but not from the one it is doing the hosting.
From computer A with an ip address of 75.105.160, I can connect to 12.147.122.14:8085.
From computer B with an ip address of 12.147.122.14, I cannot connect to 12.147.122.14:8085.
The message is taking too long to respond.
The net diag> connect iphost 12.147.122.14 8085 responds with [none].
It makes no difference if the firewall is on or off.

This did work on a Linksys router. The router I am now using is a Ruckus VF2825. The CEO of
the broadband wireless confirms the router is set up properly and is working properly. (He recommended replacing the
Linksys with the Ruckus).

Do you have any suggestions?

bswanson, looks like there is a missing digit in the IP address of computer A. Where is computer A? On the Internet, ie behind the WAN port of the 2825?

When testing this on computer B, you are trying to reach port 8085 on its own IP address? Traffic shouldn’t exit computer B’s NIC as it is destined for itself. Where is computer B? Wired? Wireless?

Which firmware version is running on the 2825?

Ruckus Support

BigDog,

Compurter A is behind ip address 75.105.199.160 on a Linksys router. It can see the sit on ip address 12.147.122.14:8085 which is the 2825 redirecting the service to the server 192.168.1.225:8085.

Computer B is wired to the 2825.

The main thing I want to check is can the server be reached from the internet.

The ip 75.147.122.14 will be dropped when the contract runs out.

There is no problem in connecting to 192.168.1.225 from 192.168.1.103. The problem comes in if I use the external ip 12.147.122.14 which is the 2825 address on the WAN.

Bill, I just found out that Port Forwarding rules are NOT applied when traffic is sent by a station on the private network. In your example, trying to access the public IP address of the 2825 from a station which is connected to your private network will not trigger the Port Forwarding rule. Only for traffic originated from a station on the WAN side, the 2825 will apply Port Forwarding rules.

I’m afraid the only way to test the reachability of your internal webserver is to try this from another station on the Internet.

Ruckus Support