Belkin Virtual Server Problem

Brainfire · 18-09-2006, 21:04

After a horrible experience and a week of swearing at a Linksys WRT54G (would only allow one wireless connection, and a very poor one at that), I took it back and swapped it for a Belkin F5D7230UK4 which works great... great, apart from one thing...

With the Linksys I could use my Remote connection (Both Windows Remote Desktop and VNC) no problem. The setup on the PC hasn't changed, so it isn't that, therefore it must be the Belkin router at fault.

There is no port forwarding with this router, only virtual servers, which apparently won't let me connect no matter what. The connections work ok as I can get them working ok over the LAN using IP addresses, but no way will they work using my dyndns hostname and a browser. I've even tried switching off the router's firewall (no XP firewall running), but still the same.

The one thing which doesn't look right to me is despite the PC having a static IP of 192.168.0.5 the router still shows it in the connected clients list as 192.168.0.100 - The DHCP on the router is set to assign addresses from 100 > 120. Idea's anyone, before this one goes back as well??

DocDutch · 19-09-2006, 09:17

1st of all

which ports have you opened for RDS and for VNC and have you put them to your own ip address.

also have you restarted the router after changing the IP address of the DHCP. as this could be the reason why its not working properly.

Brainfire · 19-09-2006, 10:45

Hi, sorry about the lack of introduction on the first post, but when you have problems you just want them fixed, eh? How did we ever live without our PC's, I wonder???

The ports for Remote Desktop are 3389 and 6969, both TCP - I changed the last one myself for security reasons in that it keeps the usual port 80 out of the equation.

The TightVNC is running on 5800 & 5900, both TCP - and all these ports point to the PC, which is 192.168.0.5

I reset the router back to factory defaults last night, and it seems to have fixed the allocation problem for the PC of 192.168.0.100 when it is actually a static IP of 192.168.0.5 - I'll need to try the Virtual Servers again tonight as it was too late for it last night - There's probably a good chance that since it's not now seeing the PC as a DHCP address it'll work - I'll let you know.

**Graham M** · 19-09-2006, 11:27

Check the IPs attached to the Belkin router because most Belkin routers I've come accross (including brand new) have assigned IP addresses in the range 192.169.2.x

Brainfire · 19-09-2006, 14:32

Quote:

Originally Posted by Zeph

Check the IPs attached to the Belkin router because most Belkin routers I've come accross (including brand new) have assigned IP addresses in the range 192.169.2.x

Yeah, it did come configured with that address range, but I never left it as that as I prefer the 192.168.0.xxx for various reasons. It shouldn't make any difference what it is as it's only another node on your LAN, and as long as it talks to your cable modem, it makes no difference.

Anyway, like I said above, the router has now been reset, the Virtual Server ports, etc, set up again and.......... it's still the bloody same!! One call or email to Belkin tech support, and if it doesn't work after that it's going back pronto.