Re: RDC through linksys router

From: Sooner Al (SoonerAl_at_somewhere.net.invalid)
Date: 12/07/04 

Date: Tue, 7 Dec 2004 11:22:58 -0600

Lanwench...

That link has changed to...

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

Later... 

-- 
    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...
"Lanwench [MVP - Exchange]" <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in 
message news:u3p7QxH3EHA.3708@TK2MSFTNGP14.phx.gbl...
> Chris wrote:
>> <<Message:
>>
>> The client could not connect to the remote computer.
>> Remote connections might not be enabled or the computer might be too
>> busy to accept new connections. It is also possible that network
>> problems are preventing your connection.
>> Please try connecting again later. >>
>>
>>
>> When i try to remotely access a client's computer, this is the error
>> message i get. However, when i access the clients server, and through
>> the server, access his computer, i am able to do so immediately.
>>
>> Is there any way to set up a specific port on the router, and also on
>> the clients computer, so i can actually get it to work from outside of
>> the lan. I know that the default port for remote access is 3389, so
>> can i add a port, or is there a procedure i can follow to get it
>> working.
>>
>> I have the port forwarding set up on the router, and assigned a port
>> to the client computer (among others) and all computers work except
>> this one. I did find remote access software that didnt belong,
>> computer has been checked for outside programs, and registry has been
>> revised, everything seems to look up to par to all the other
>> computers.
>>
>> Any ideas would be greatly appreciated.
>>
>> Chris
>
> You can open up port 3389 to whatever you want in your router/firewall, but
> if you don't have multiple public IP addresses, it's a pain in the ___.
> You'd also need DHCP reservations or static IPs on the clients.
> See if http://members.cox.net/ajarvi/RemoteDesktop/Multiple_PC_RD.html helps
> at all?
>
>

Relevant Pages

  • Re: Virtual redirect of COM port.
    ... But isn't that only for printers connecting via the serial port? ... Is it possible to connect another serial device to the clients com ... > Prerequisites Windows 2003 Terminal Server ... > double-click Terminal Services Connections) ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Help: Torrent dowload question
    ... Try entering the server name listed in the torrent Announce URL ... me the exact port, I'll be greatful). ... Most modern BitTorrent clients ... BitTorrent clients make three kinds of connections: ...
    (rec.motorcycles.dirt)
  • RE: Remote Access switching off - Error 913
    ... The port is already configured as you describe - the issue is that clients ... run the remote access wizard again from server management. ...
    (microsoft.public.windows.server.sbs)
  • Re: RDC through linksys router
    ... > The client could not connect to the remote computer. ... However, when i access the clients server, and through ... I know that the default port for remote access is 3389, ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: How can I make the server to call back to client without being blocked by firewall.
    ... how can we pick a port which is guaranteed to be usable? ... >>> connection to any one of others via our server. ... >>> an always on TCP connections from the clients to our server may solve ...
    (comp.security.firewalls)