Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Windows XP / Remote Desktop / June 2007

Tip: Looking for answers? Try searching our database.

Your Remote Desktop Session has ended

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Bean - 07 Jun 2007 18:20 GMT
I have 2 PCs at home that I make remote desktop connections to from work.  
Both are XP SP2.  I forward port 3389 to PC1 and port 3391 to PC2 on my
router.  I changed the listening port for Remote Desktop to 3391 on PC2.  RDP
connections to PC1 work w/o any problems.  From within my local network, I
can connect to PC2 (xxxxx.no-ip.com:3391) with no problems.  However, from
work it starts to connect (it has PC2- xxxxx.no-ip.com:3391 Remote Desktop on
the menu bar) and then after 10-15 seconds I get the following error:

Your Remote Desktop session has ended.
The connection to the remote computer was lost, possibly due to network
connectivity problems.  Try connecting to the remote computer again.  If the
problem continues, contact your network administrator or technical support.

I have the same problem with Zone Alarm turned off.  so I don't think it's a
firewall issue, and there is nothing to speak of in the Event Logs.

Any ideas?

Thanks,

Nelson
Sooner Al [MVP] - 07 Jun 2007 18:43 GMT
>I have 2 PCs at home that I make remote desktop connections to from work.
> Both are XP SP2.  I forward port 3389 to PC1 and port 3391 to PC2 on my
[quoted text clipped - 22 lines]
>
> Nelson

Any chance the folks at work are blocking TCP Port 3391 outbound? You can
check with the work network admins about that. Can you connect to PC2 from
another location like a friends house or the library or your favorite
bar/restaurant?

Have you tried to simply reset the router?

Signature

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...
How to ask a question
http://support.microsoft.com/KB/555375

Bean - 07 Jun 2007 20:27 GMT
I tried reseting the router w/o success.  I have not tried from a location
other than work, but I have been assured by the network-gods here at work
that 3391 is not blocked.  I'm fairly certain I'm getting past the router.  
The remote desktop window appears and the name of the PC is being resolved
and is visible in the menu bar - PC2- xxxxx.no-ip.com:3391 before the error
pops up.

> >I have 2 PCs at home that I make remote desktop connections to from work.
> > Both are XP SP2.  I forward port 3389 to PC1 and port 3391 to PC2 on my
[quoted text clipped - 29 lines]
>
> Have you tried to simply reset the router?
Sooner Al [MVP] - 08 Jun 2007 11:00 GMT
>I tried reseting the router w/o success.  I have not tried from a location
> other than work, but I have been assured by the network-gods here at work
[quoted text clipped - 3 lines]
> error
> pops up.

I would still try from another location than work as a test...

You also might try a different high number port for PC2, ie. 45678 for
example..

What router are you using? I presume you have the latest firmware installed?

Signature

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...
How to ask a question
http://support.microsoft.com/KB/555375

Bean - 12 Jun 2007 20:02 GMT
Sorry for the delay in getting back to you.  My router is a Netgear WGT624
with the latest firmware (V4.2.4_1.0.1).  I tried on another port with the
same results.  Here is what may be a big clue.  I tried connecting from
several PCs at work.  Desktops could not connect, while laptops could?!?!  
How's that for a noggin scratcher?

> >I tried reseting the router w/o success.  I have not tried from a location
> > other than work, but I have been assured by the network-gods here at work
[quoted text clipped - 10 lines]
>
> What router are you using? I presume you have the latest firmware installed?
Sooner Al [MVP] - 13 Jun 2007 17:44 GMT
> Sorry for the delay in getting back to you.  My router is a Netgear WGT624
> with the latest firmware (V4.2.4_1.0.1).  I tried on another port with the
> same results.  Here is what may be a big clue.  I tried connecting from
> several PCs at work.  Desktops could not connect, while laptops could?!?!
> How's that for a noggin scratcher?

Did you ever try from a location other than work?

Any chance the laptops are running some sort of firewall or VPN or some type
of security software that may block this? I have seen reports of a Cisco VPN
client blocking RDP requests.

Can the laptops connect to PC1 on TCP Port 3389?

Signature

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...
How to ask a question
http://support.microsoft.com/KB/555375

Sooner Al [MVP] - 13 Jun 2007 18:38 GMT
>> Sorry for the delay in getting back to you.  My router is a Netgear
>> WGT624
[quoted text clipped - 11 lines]
>
> Can the laptops connect to PC1 on TCP Port 3389?

Well, I got desktops and laptops mixed up as you can tell. So just
substitute and let us know...

Signature

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...
How to ask a question
http://support.microsoft.com/KB/555375

Bean - 13 Jun 2007 20:53 GMT
- My boss connected to PC2 from his home PC with no problems.  
- The laptops can connect to PC1 on TCP Port 3389 with no problems.
- I made sure Windows firewall was turned off on the desktop and the problem
is still there.  There is no VPN software on the desktop(s)

**  I also created a fresh install of XP on a virtual machine and did not
join it to the domain to eliminate any possibility that there was a policy in
effect that might cause the problem.  Connecting to PC1 on 3389 from the
virtual machine worked on my desktop and on a laptop.  Connecting to PC2 on
3391 from the virtual machine failed on my desktop and failed on the laptop.
**

Thanks for continuing to help on this Al.

> >> Sorry for the delay in getting back to you.  My router is a Netgear
> >> WGT624
[quoted text clipped - 14 lines]
> Well, I got desktops and laptops mixed up as you can tell. So just
> substitute and let us know...
Sooner Al [MVP] - 13 Jun 2007 21:08 GMT
>- My boss connected to PC2 from his home PC with no problems.
> - The laptops can connect to PC1 on TCP Port 3389 with no problems.
[quoted text clipped - 13 lines]
>
> Thanks for continuing to help on this Al.

Well, if you or someone can connect to your home PC1 (TCP Port 3389) and PC2
(TCP Port 3391) from a site other than the work LAN then it comes down to
something on the desktop PCs at work blocking the connection to PC2.
Obviously the laptops are configured different than the desktops.

Have you looked at the event logs on the work desktop clients to see if you
can find any clues?

What OS is running on the work desktops?

What version of the Remote Desktop client are you running on the laptops and
the desktops at work?

Signature

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...
How to ask a question
http://support.microsoft.com/KB/555375

Bean - 14 Jun 2007 01:52 GMT
I checked the event logs on all the desktops that failed to connect and found
nothing of interest.  All desktops and laptops run XP SP2.  The Remote
Desktop clients on the laptops and desktops are Shell version 6.0 (Build
number 6000).

I find it interesting... strange... spooky... that on a laptop that has no
problem conecting to PC2 on 3391 can connect to PC1 on 3389 on a virtual
machine running on the laptop but cannot connect to PC2 on 3391 through the
virtual machine.

> >- My boss connected to PC2 from his home PC with no problems.
> > - The laptops can connect to PC1 on TCP Port 3389 with no problems.
[quoted text clipped - 26 lines]
> What version of the Remote Desktop client are you running on the laptops and
> the desktops at work?
Bean - 21 Jun 2007 20:41 GMT
I found the problem.  It turns out the MTU on my router was set to 1400.  I
changed this to 1500 and could connect to PC2.

> I checked the event logs on all the desktops that failed to connect and found
> nothing of interest.  All desktops and laptops run XP SP2.  The Remote
[quoted text clipped - 36 lines]
> > What version of the Remote Desktop client are you running on the laptops and
> > the desktops at work?
Sooner Al [MVP] - 21 Jun 2007 20:49 GMT
>I found the problem.  It turns out the MTU on my router was set to 1400.  I
> changed this to 1500 and could connect to PC2.

Strange indeed...

Thanks for the feedback. Glad to hear you have it fixed...

Signature

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...
How to ask a question
http://support.microsoft.com/KB/555375

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.