Welcome to WinForumz.com!
FAQFAQ      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

Linksys BEFSR41 Router, Microsoft Remote Desktop Connectio..

 
   Windows XP (Home) -> Work Remotely RSS
Next:  Codec not installed on Movie Maker  
Author Message
Bob Felton

External


Since: Aug 01, 2005
Posts: 9



(Msg. 1) Posted: Wed Aug 01, 2007 3:38 pm
Post subject: Linksys BEFSR41 Router, Microsoft Remote Desktop Connection Problem
Archived from groups: microsoft>public>windowsxp>work_remotely (more info?)

Almost consistently, whenever I connect to a remote machine using RDT,
the connection will break after a minute or so. If I try to connect
to a different computer at the same IP address after the first
connection was broken, I get a message back saying "This computer
can't connect to the remote computer." If I wait about 15 minutes, I
can again connect to either computer and the situation then repeats
itself. One computer is running Windows Server 2003 R2 SP2, the other
is running Windows XP Professional SP2. My computer is running
Windows XP Professional SP2.

I connect using IP:portx, with a different port for each computer at
the remote location. The router has port redirection set up for each
portx to route the connection to the proper computer using the
standard RDT port of 3389.

I can connect to either computer, but when one breaks, they both
break. During the time RDT will not connect, I can connect to an FTP
server, send email through an email server, and administer the email
server at the same IP address, using the respective ports for the
functions. And, I can connect to a computer at an entirely different
IP address using RDT. The FTP, email administration, and RDT
connection to the other IP address never break. Thus, I think I can
rule out anything at my end including my router and my ISP. It would
seem to me the problem lies in the router at the location of the
computers to which the RDT connection is breaking: Linksys BEFSR41.

The remote location IP addresses are static and the individual
computer IP addresses at the respective locations are static.

Can anyone provide any assistance with this matter? Thank you.
--
Bob Felton

 >> Stay informed about: Linksys BEFSR41 Router, Microsoft Remote Desktop Connectio.. 
Back to top
Login to vote
Sooner Al [MVP]

External


Since: Feb 03, 2005
Posts: 385



(Msg. 2) Posted: Thu Aug 02, 2007 5:06 am
Post subject: Re: Linksys BEFSR41 Router, Microsoft Remote Desktop Connection Problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

"Bob Felton" <bob123.removethis.RemoveThis@fieldtown.net> wrote in message
news:rm22b31nn00f2apcruqqmjio861qqeuc7c@4ax.com...
> Almost consistently, whenever I connect to a remote machine using RDT,
> the connection will break after a minute or so. If I try to connect
> to a different computer at the same IP address after the first
> connection was broken, I get a message back saying "This computer
> can't connect to the remote computer." If I wait about 15 minutes, I
> can again connect to either computer and the situation then repeats
> itself. One computer is running Windows Server 2003 R2 SP2, the other
> is running Windows XP Professional SP2. My computer is running
> Windows XP Professional SP2.
>
> I connect using IP:portx, with a different port for each computer at
> the remote location. The router has port redirection set up for each
> portx to route the connection to the proper computer using the
> standard RDT port of 3389.
>
> I can connect to either computer, but when one breaks, they both
> break. During the time RDT will not connect, I can connect to an FTP
> server, send email through an email server, and administer the email
> server at the same IP address, using the respective ports for the
> functions. And, I can connect to a computer at an entirely different
> IP address using RDT. The FTP, email administration, and RDT
> connection to the other IP address never break. Thus, I think I can
> rule out anything at my end including my router and my ISP. It would
> seem to me the problem lies in the router at the location of the
> computers to which the RDT connection is breaking: Linksys BEFSR41.
>
> The remote location IP addresses are static and the individual
> computer IP addresses at the respective locations are static.
>
> Can anyone provide any assistance with this matter? Thank you.
> --
> Bob Felton

I would...

1. Make sure the router firmware is the latest available.
2. Reflash the firmware to see if that help.
3. Try port forwarding versus port redirection to see if the router is
having a problem with redirection. See option 1...

http://theillustratednetwork.mvps.org/RemoteDesktop/Multiple_PC_RD.html

IMO, the best solution would be to setup a VPN or SSH tunnel and access all
the PCs through one hole versus multiple holes in the router.

--

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

 >> Stay informed about: Linksys BEFSR41 Router, Microsoft Remote Desktop Connectio.. 
Back to top
Login to vote
Bob Felton

External


Since: Aug 01, 2005
Posts: 9



(Msg. 3) Posted: Sat Aug 04, 2007 6:19 pm
Post subject: Re: Linksys BEFSR41 Router, Microsoft Remote Desktop Connection Problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

I have determined the router's firmware is not at latest version. I
will update it as soon as I can.

uPNP port forwarding in the router is being used. It allows an
incoming port to be forwarded to a specific LAN IP and a specific
(same or different) port.

RDP is being used as it was easy to implement with no extra equipment
or software required. It worked fine when the server was a Windows
2000 Server based server. As best as I can recall, the problem only
started once the server was changed to a Windows Server 2003 R2 SP2
based server (new platform as well). So, there may be something
different about how remote access worked under Windows 2000 Server
versus how it works under Windows Server 2003 as well. It could very
well not be a router issue at all.


On Thu, 2 Aug 2007 05:06:25 -0500, "Sooner Al [MVP]"
<SoonerAl.TakeThisOut@somewhere.net.invalid> wrote:

>"Bob Felton" <bob123.removethis.TakeThisOut@fieldtown.net> wrote in message
>news:rm22b31nn00f2apcruqqmjio861qqeuc7c@4ax.com...
>> Almost consistently, whenever I connect to a remote machine using RDT,
>> the connection will break after a minute or so. If I try to connect
>> to a different computer at the same IP address after the first
>> connection was broken, I get a message back saying "This computer
>> can't connect to the remote computer." If I wait about 15 minutes, I
>> can again connect to either computer and the situation then repeats
>> itself. One computer is running Windows Server 2003 R2 SP2, the other
>> is running Windows XP Professional SP2. My computer is running
>> Windows XP Professional SP2.
>>
>> I connect using IP:portx, with a different port for each computer at
>> the remote location. The router has port redirection set up for each
>> portx to route the connection to the proper computer using the
>> standard RDT port of 3389.
>>
>> I can connect to either computer, but when one breaks, they both
>> break. During the time RDT will not connect, I can connect to an FTP
>> server, send email through an email server, and administer the email
>> server at the same IP address, using the respective ports for the
>> functions. And, I can connect to a computer at an entirely different
>> IP address using RDT. The FTP, email administration, and RDT
>> connection to the other IP address never break. Thus, I think I can
>> rule out anything at my end including my router and my ISP. It would
>> seem to me the problem lies in the router at the location of the
>> computers to which the RDT connection is breaking: Linksys BEFSR41.
>>
>> The remote location IP addresses are static and the individual
>> computer IP addresses at the respective locations are static.
>>
>> Can anyone provide any assistance with this matter? Thank you.
>> --
>> Bob Felton
>
>I would...
>
>1. Make sure the router firmware is the latest available.
>2. Reflash the firmware to see if that help.
>3. Try port forwarding versus port redirection to see if the router is
>having a problem with redirection. See option 1...
>
>http://theillustratednetwork.mvps.org/RemoteDesktop/Multiple_PC_RD.html
>
>IMO, the best solution would be to setup a VPN or SSH tunnel and access all
>the PCs through one hole versus multiple holes in the router.

--
Bob Felton
 >> Stay informed about: Linksys BEFSR41 Router, Microsoft Remote Desktop Connectio.. 
Back to top
Login to vote
Sooner Al [MVP]

External


Since: Feb 03, 2005
Posts: 385



(Msg. 4) Posted: Sun Aug 05, 2007 6:28 am
Post subject: Re: Linksys BEFSR41 Router, Microsoft Remote Desktop Connection Problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

"Bob Felton" <bob123.removethis DeleteThis @fieldtown.net> wrote in message
news:h19ab3l4oqc5am8uu9vv9j6jlnjvrjmght@4ax.com...
>I have determined the router's firmware is not at latest version. I
> will update it as soon as I can.
>
> uPNP port forwarding in the router is being used. It allows an
> incoming port to be forwarded to a specific LAN IP and a specific
> (same or different) port.
>
> RDP is being used as it was easy to implement with no extra equipment
> or software required. It worked fine when the server was a Windows
> 2000 Server based server. As best as I can recall, the problem only
> started once the server was changed to a Windows Server 2003 R2 SP2
> based server (new platform as well). So, there may be something
> different about how remote access worked under Windows 2000 Server
> versus how it works under Windows Server 2003 as well. It could very
> well not be a router issue at all.
>
>
>
What version of the Remote Desktop Client are you running, ie. the new RDP 6
client or older?

Are you running Terminal Server on the W2K3 server box?

You might consider posting this to the
microsoft.public.windows.terminal_services or
microsoft.public.windows.server.networking news groups.

--

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
 >> Stay informed about: Linksys BEFSR41 Router, Microsoft Remote Desktop Connectio.. 
Back to top
Login to vote
Bob Felton

External


Since: Aug 01, 2005
Posts: 9



(Msg. 5) Posted: Mon Aug 06, 2007 10:00 pm
Post subject: Re: Linksys BEFSR41 Router, Microsoft Remote Desktop Connection Problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

The RDP client is whatever the latest is via Windows Update. No,
Terminal Services is not the target at the server. I am using RDP at
the server.

If I won't get chewed out for cross-posting, I will post to another
group if you think that would be advisable.


On Sun, 5 Aug 2007 06:28:05 -0500, "Sooner Al [MVP]"
<SoonerAl.DeleteThis@somewhere.net.invalid> wrote:

>"Bob Felton" <bob123.removethis.DeleteThis@fieldtown.net> wrote in message
>news:h19ab3l4oqc5am8uu9vv9j6jlnjvrjmght@4ax.com...
>>I have determined the router's firmware is not at latest version. I
>> will update it as soon as I can.
>>
>> uPNP port forwarding in the router is being used. It allows an
>> incoming port to be forwarded to a specific LAN IP and a specific
>> (same or different) port.
>>
>> RDP is being used as it was easy to implement with no extra equipment
>> or software required. It worked fine when the server was a Windows
>> 2000 Server based server. As best as I can recall, the problem only
>> started once the server was changed to a Windows Server 2003 R2 SP2
>> based server (new platform as well). So, there may be something
>> different about how remote access worked under Windows 2000 Server
>> versus how it works under Windows Server 2003 as well. It could very
>> well not be a router issue at all.
>>
>>
>>
>What version of the Remote Desktop Client are you running, ie. the new RDP 6
>client or older?
>
>Are you running Terminal Server on the W2K3 server box?
>
>You might consider posting this to the
>microsoft.public.windows.terminal_services or
>microsoft.public.windows.server.networking news groups.

--
Bob Felton
 >> Stay informed about: Linksys BEFSR41 Router, Microsoft Remote Desktop Connectio.. 
Back to top
Login to vote
Sooner Al [MVP]

External


Since: Feb 03, 2005
Posts: 385



(Msg. 6) Posted: Tue Aug 07, 2007 4:49 am
Post subject: Re: Linksys BEFSR41 Router, Microsoft Remote Desktop Connection Problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

"Bob Felton" <bob123.removethis.DeleteThis@fieldtown.net> wrote in message
news:qqufb3ti4be1f13bnecgft52hd36t6kpod@4ax.com...
> The RDP client is whatever the latest is via Windows Update. No,
> Terminal Services is not the target at the server. I am using RDP at
> the server.
>
> If I won't get chewed out for cross-posting, I will post to another
> group if you think that would be advisable.
>
>
>
> --
> Bob Felton


Other than looking at the logs on both the client and host I think your only
recourse is to post to those other groups...

--

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
 >> Stay informed about: Linksys BEFSR41 Router, Microsoft Remote Desktop Connectio.. 
Back to top
Login to vote
Bob Felton

External


Since: Aug 01, 2005
Posts: 9



(Msg. 7) Posted: Tue Aug 21, 2007 3:59 pm
Post subject: Re: Linksys BEFSR41 Router, Microsoft Remote Desktop Connection Problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

I have not posted to the other site as yet.

Even after updating the router firmware, the problem still exists.
However, I now believe it is related to a screensaver timeout.

The problem happens when I use RDP to log into the Windows Server 2003
R2 SP2 as Administrator when the console is logged in as another user
(Backup). For console logins, the screensaver timeout is set to 1
minunte for user Administrator and 3 minutes for user Backup. The RDP
connection is dropped after about 3 minutes - strangely close to the
screensaver timeout of the user logged in on the console. Why the RDP
drop out affects RDP into a completely different machine is still an
unknown.


On Tue, 7 Aug 2007 04:49:24 -0500, "Sooner Al [MVP]"
<SoonerAl.TakeThisOut@somewhere.net.invalid> wrote:

>"Bob Felton" <bob123.removethis.TakeThisOut@fieldtown.net> wrote in message
>news:qqufb3ti4be1f13bnecgft52hd36t6kpod@4ax.com...
>> The RDP client is whatever the latest is via Windows Update. No,
>> Terminal Services is not the target at the server. I am using RDP at
>> the server.
>>
>> If I won't get chewed out for cross-posting, I will post to another
>> group if you think that would be advisable.
>>
>>
>>
>> --
>> Bob Felton
>
>
>Other than looking at the logs on both the client and host I think your only
>recourse is to post to those other groups...

--
Bob Felton
 >> Stay informed about: Linksys BEFSR41 Router, Microsoft Remote Desktop Connectio.. 
Back to top
Login to vote
Bob Felton

External


Since: Aug 01, 2005
Posts: 9



(Msg. 8) Posted: Tue Sep 18, 2007 4:28 pm
Post subject: Re: Linksys BEFSR41 Router, Microsoft Remote Desktop Connection Problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

I resolved the issue by using the fix shown in
http://terminal.servebeer.com/php/flaky_connections.php (which was
provided to me by Coraleigh Miller in the server/general forum). That
fix along with reverting to the version 5 RDP client resolved my
connection issues. Even with the fixes shown in the article,
connection dropouts still happened when using the version 6 RDP
client.


On Tue, 21 Aug 2007 15:59:10 -0700, Bob Felton
<bob123.removethis RemoveThis @fieldtown.net> wrote:

>I have not posted to the other site as yet.
>
>Even after updating the router firmware, the problem still exists.
>However, I now believe it is related to a screensaver timeout.
>
>The problem happens when I use RDP to log into the Windows Server 2003
>R2 SP2 as Administrator when the console is logged in as another user
>(Backup). For console logins, the screensaver timeout is set to 1
>minunte for user Administrator and 3 minutes for user Backup. The RDP
>connection is dropped after about 3 minutes - strangely close to the
>screensaver timeout of the user logged in on the console. Why the RDP
>drop out affects RDP into a completely different machine is still an
>unknown.
>
>
>On Tue, 7 Aug 2007 04:49:24 -0500, "Sooner Al [MVP]"
><SoonerAl RemoveThis @somewhere.net.invalid> wrote:
>
>>"Bob Felton" <bob123.removethis RemoveThis @fieldtown.net> wrote in message
>>news:qqufb3ti4be1f13bnecgft52hd36t6kpod@4ax.com...
>>> The RDP client is whatever the latest is via Windows Update. No,
>>> Terminal Services is not the target at the server. I am using RDP at
>>> the server.
>>>
>>> If I won't get chewed out for cross-posting, I will post to another
>>> group if you think that would be advisable.
>>>
>>>
>>>
>>> --
>>> Bob Felton
>>
>>
>>Other than looking at the logs on both the client and host I think your only
>>recourse is to post to those other groups...

--
Bob Felton
 >> Stay informed about: Linksys BEFSR41 Router, Microsoft Remote Desktop Connectio.. 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
Linksys Router Remote Desktop. - Ok... so one one of my networks ive been able to disable the DHCP function of my linksys router and forward port number 3389 (remote desktop port) to the IP address i wanted and it works great..... On my second network... ive done the same thing.....

Remote Desktop Connection and Linksys Router - Hi- I have a desktop set up in my dorm room on a college campus that is connected to the internet through a Linksys WRT54GS router. I want to connect to this desktop from anywhere on the Internet through my laptop. Both computers have Windows XP Pro....

bypass linksys wrt54gs router using remote desktop. - The only way to access my desktop away from home with my laptop is to remove the router and just use the modem. I have already opened port 8080 on router but sill had no success. Can someone give me any suggestions?

Linksys BEFSR41 / RV082 Connection - My company recently installed a Linksys RV082 to allow VPN connections into work. At home, I have a Linksys BEFSR41 3.1 router with firmware version 1.05. I cannot connect in to work if I connect in through the router (either wirelessly or hardwired). ...

remote desktop behind a router - Hoping you folks can help out with this problem. 1. 2 clients, 1 laptop (wireless), 1 desktop (wired), both set up as remote desktop clients and servers. 2. network everywhere router 3. remote desktop (web client and RDP client) work fine on lan side o...
   Windows XP (Home) -> Work Remotely All times are: Eastern Time (US & Canada) (change)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum

Categories:
  Windows XP
 Windows Vista!
 Win 2000/NT/98/ME


[ Contact us | Terms of Service/Privacy Policy ]