Cable Forum - View Single Post

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.

19-09-2006, 10:45	#3
Brainfire Inactive Join Date: Sep 2006 Posts: 3	Re: Belkin Virtual Server Problem 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.