|
#1
|
|||
|
|||
|
I don't think this is a MS issue but I've tried everywhere and everything
else. I need to remotely access computers at work for troubleshooting. They are behind a dsl modem (with a static WAN IP) and then behind a NAT router. I have five machines, each with a static IP, each has been setup to use and allow remote desktop connections all using different RDP ports (ie 3391, 3392, 3393, etc). On the router, all ports have been forwarded to the respective IP's, ie: port 3391 gets forwarded to 192.168.1.3 port 3391. Windows firewall has also been turned off on all machines and there isn't any other firewall programs running. So a remote desktop logon looks like this: internetIPofRemotePC:339x So here is the problem, I can only connect remotely to one computer, when trying to connect to the other machines (not at the same time) I get an unable to connect error. All settings are the same on each computer. I can however connect to each computer locally when connected to the lan. So that tells me that remote desktop is working properly but either the router or the modem is configured incorrectly. When I connect internally I can connect using the IP of the lan machine or it's computer name both followed by the unique RDP port, If it matters, the dsl modem is a netopia 3546 002 and the router is a linksys wrt51ag. Any ideas? |
|
#2
|
|||
|
|||
|
Well, if you can connect to each PC over the local LAN from another PC on
the local LAN then it comes down to a port forwarding issue with the router or the DSL modem. You can run the http://www.canyouseeme.org test from each PC. If the test fails then you need to resolve the port forwarding issue. You can isolate further by removing the router and connecting each PC individually to the modem. If the test still fails then its an issue with the DSL modem. Some DSL modems also act as routers so you would need to figure out how to forward ports through the modem... -- Al Jarvi (MS-MVP Windows Networking) Please post *ALL* questions and replies to the news group for the mutual benefit of all of us... The MS-MVP Program - http://mvp.support.microsoft.com This posting is provided "AS IS" with no warranties, and confers no rights... "ivwshane" <ivwshane@discussions.microsoft.com> wrote in message news:15C3EF93-94BE-4DBB-9A0B-F4CFDABD530B@microsoft.com... > I don't think this is a MS issue but I've tried everywhere and everything > else. > I need to remotely access computers at work for troubleshooting. > > They are behind a dsl modem (with a static WAN IP) and then behind a NAT > router. > > I have five machines, each with a static IP, each has been setup to use > and > allow remote desktop connections all using different RDP ports (ie 3391, > 3392, 3393, etc). On the router, all ports have been forwarded to the > respective IP's, ie: port 3391 gets forwarded to 192.168.1.3 port 3391. > Windows firewall has also been turned off on all machines and there isn't > any > other firewall programs running. > > So a remote desktop logon looks like this: > > internetIPofRemotePC:339x > > > So here is the problem, I can only connect remotely to one computer, when > trying to connect to the other machines (not at the same time) I get an > unable to connect error. All settings are the same on each computer. > > I can however connect to each computer locally when connected to the lan. > So > that tells me that remote desktop is working properly but either the > router > or the modem is configured incorrectly. > > When I connect internally I can connect using the IP of the lan machine or > it's computer name both followed by the unique RDP port, > > If it matters, the dsl modem is a netopia 3546 002 and the router is a > linksys wrt51ag. > > > Any ideas? |
|
#3
|
|||
|
|||
|
I thought your post looked familiar...:-)
http://www.broadbandreports.com/forum/remark,14848651 -- Al Jarvi (MS-MVP Windows Networking) Please post *ALL* questions and replies to the news group for the mutual benefit of all of us... The MS-MVP Program - http://mvp.support.microsoft.com This posting is provided "AS IS" with no warranties, and confers no rights... "Sooner Al [MVP]" <SoonerAl@somewhere.net.invalid> wrote in message news:OOT82ro7FHA.1032@TK2MSFTNGP11.phx.gbl... > Well, if you can connect to each PC over the local LAN from another PC on > the local LAN then it comes down to a port forwarding issue with the > router or the DSL modem. You can run the http://www.canyouseeme.org test > from each PC. If the test fails then you need to resolve the port > forwarding issue. You can isolate further by removing the router and > connecting each PC individually to the modem. If the test still fails then > its an issue with the DSL modem. Some DSL modems also act as routers so > you would need to figure out how to forward ports through the modem... > > -- > > Al Jarvi (MS-MVP Windows Networking) > > Please post *ALL* questions and replies to the news group for the mutual > benefit of all of us... > The MS-MVP Program - http://mvp.support.microsoft.com > This posting is provided "AS IS" with no warranties, and confers no > rights... > > "ivwshane" <ivwshane@discussions.microsoft.com> wrote in message > news:15C3EF93-94BE-4DBB-9A0B-F4CFDABD530B@microsoft.com... >> I don't think this is a MS issue but I've tried everywhere and everything >> else. >> I need to remotely access computers at work for troubleshooting. >> >> They are behind a dsl modem (with a static WAN IP) and then behind a NAT >> router. >> >> I have five machines, each with a static IP, each has been setup to use >> and >> allow remote desktop connections all using different RDP ports (ie 3391, >> 3392, 3393, etc). On the router, all ports have been forwarded to the >> respective IP's, ie: port 3391 gets forwarded to 192.168.1.3 port 3391. >> Windows firewall has also been turned off on all machines and there isn't >> any >> other firewall programs running. >> >> So a remote desktop logon looks like this: >> >> internetIPofRemotePC:339x >> >> >> So here is the problem, I can only connect remotely to one computer, when >> trying to connect to the other machines (not at the same time) I get an >> unable to connect error. All settings are the same on each computer. >> >> I can however connect to each computer locally when connected to the lan. >> So >> that tells me that remote desktop is working properly but either the >> router >> or the modem is configured incorrectly. >> >> When I connect internally I can connect using the IP of the lan machine >> or >> it's computer name both followed by the unique RDP port, >> >> If it matters, the dsl modem is a netopia 3546 002 and the router is a >> linksys wrt51ag. >> >> >> Any ideas? > > |
|
#4
|
|||
|
|||
|
So it turns out that it was a microsoft issue:|
Unfortunately I couldn't pin point exactly what it was so I just formatted and reinstalled windows XP, disabled the firewall, changed the rpd ports and all is working now ![]() To be fair though, I wasn't the one that originally installed windows so it could have been something the original installer did or something caused the malfunction like another piece of software. Either way I'm happy now ![]() |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Monitor Stops Working after Remote Desktop Session | Venkat V | Windows XP Work Remotely | 2 | 01-05-2006 07:15 AM |
| Moving Remote Desktop destroys mouse pointer scheme. | theyas@community.nospam | Windows XP Work Remotely | 1 | 01-05-2006 07:14 AM |
| Remote Desktop - suddenly can't connect! | Stroller | Windows XP Work Remotely | 18 | 01-05-2006 07:13 AM |
| Remote Desktop Not Working | rcir88 | Windows XP Work Remotely | 1 | 01-05-2006 07:12 AM |
| Remote Desktop doesn't work properly (network issue) | christophesav | Windows XP Network Web | 0 | 01-05-2006 04:06 AM |