Jump to content
Posted 06 January 2010 - 04:48 AM
Posted 06 January 2010 - 04:49 AM
Posted 06 January 2010 - 05:28 AM
Posted 06 January 2010 - 12:32 PM
Edited by Bolsterplate, 06 January 2010 - 12:33 PM.
Posted 06 January 2010 - 12:41 PM
Sorry maybe i didnt explain it i have tried with just one machine i.e the port 3389 forwarded to 192.168.2.4 as the only rule and still no luck. I have a cable connecton from virgin media in the UK if thats any help
I'm sure you know that since you have two workstations, each instance of Terminal Services port forwarding on your router needs to use a different port. Since 3389 is the default port for Terminal Services, you may want to troubleshoot by creating only one port forwarding rule to one workstation using the default port of 3389. Delete the other rule. If that works, then you need to use a different port for the second workstation. Use regedit on the second workstation to change the Terminal Services port from 3398 to the different port and create the second port forwarding rule using the different port.
If that's squared away, you have DSL, and you still cannot connect, you may want to try lowering the MTU on the target workstations to 1492.
Here is an article I clipped that explains how to do it for Vista and better:
Fortunately, Microsoft now allows us to adjust the MTU using the "netsh" command. As other commands in Windows Vista, you run "netsh" using the command window, in Administrative mode.
To see what interfaces you have on your computer, type
netsh interface ipv4 show subinterfaces
To change the MTU, type
netsh interface ipv4 set subinterface "Local Area Connection" mtu=nnnn store=persistent
Local Area Connection is the name of the network connection on your computer, from the list obtained above.
nnnn is the desired value for MTU.
Reboot after making the change.
Edited by TheStalker, 06 January 2010 - 12:44 PM.
Posted 06 January 2010 - 12:47 PM
Posted 06 January 2010 - 12:54 PM
Posted 06 January 2010 - 12:59 PM
I checked that website and followed how to do it for my router and that was how i was doing it in the first place
If you can connect from other computers on your lan the problem must be in your port forwarding.
Look up your router at portforward.com and it should tell you how to configure it with directions specific to your model.
One thing you might also try, is termporarily setting your dmz in your router to your local address and see if you can connect to it remotely then. With the dmz set, all ports are open and pointed to your computer so it should work. Don't leave this setting like this, just do it for a troubleshoot. If you set your dmz and you still can't connect, then your cablemodem may be a router as well. This could mean that even if your belkin router is configured properly, your modem has that port closed before data reaches your router. If you can connect remotely with the dmz set then it means your router wasn't configured properly for port forwarding before.
More and more isps are using modems that are also firewalls, and if you are unaware of this it can be a real headache trying to make this work.
Again, don't leave your dmz set. Disable the dmz again after running this test, or your ports will all be open and you will not have firewall protection.
Posted 06 January 2010 - 01:06 PM
Posted 06 January 2010 - 01:12 PM
Posted 06 January 2010 - 01:15 PM
Posted 07 January 2010 - 08:16 AM
In case I'm not able to reply, if the ISP's device is also a router, you can:
1. Eliminate your Belkin device and use the ISP's device as the only router. Set up port forwarding in the ISP's firewall. If you have the Belkin for wireless, you can disable the routing and firewall and configure it as a simple wireless access point.
2. Call your ISP and ask them how to bridge their router and how to setup your Belkin's WAN interface to work with their service. You would setup port forwarding in the Belkin.
Posted 07 January 2010 - 09:45 AM
Posted 07 January 2010 - 10:02 AM
Posted 12 January 2010 - 11:03 AM
0 members, 3 guests, 0 anonymous users