Re: Connecting to more then one computer on a network



Well, if you can connect locally over the LAN from another PC on the same
LAN then it comes down to either an addressing issue (which probably is not
the case since you can access the other PC remotely) or a port forwarding
issue. Double check port forwarding for TCP Port 3390 on the company
firewall, whatever that is. It might help if you specified the company
firewall manufacturer and model. That information may help someone with the
same firewall help you...

Its also possible that any software firewall you might be running on that
particular PC is blocking incoming Remote Desktop (RDP) requests from IP
outside the local LAN address scope. For example I do that with the built-in
XP SP2 Windows Firewall, ie. limit incoming RDP requests to my home desktop
XP Pro machines to specific local LAN IP addresses and one specific OpenVPN
client IP address.

--

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...

"Peter McCaul" <compcoff@xxxxxxxxxxx> wrote in message
news:%236EtptL3GHA.1464@xxxxxxxxxxxxxxxxxxxxxxx
Hello,

I've setup one of my users at home and I've opened up port 3389 on the
company's firewall and the user connects without a problem.

Now another user wants to connect so I've done the following:

I've made the change in the registry to have his open port read 3390.
His ip is static.
I've opened up port 3390 on the firewall.

I can't connect.

When I go to a workstaion that's on the same network and I type in the
user's internal ip 10.0.0.84:3390 it works. When I try it off site, it
doesn't connect. "The client could not
connect to the remote computer". I'm putting :3390 at the end of the
external IP when I'm off site. Logically, the problem has to be from the
firewall but I don't know what else I can do. Does anyone have a
solution?

Any help is appreciated.



.



Relevant Pages

  • Re: Remote desktop & Netgear router
    ... if you can connect to the PC from another PC using the "private LAN IP address" over your ... local LAN then Remote Desktop is obviously setup right and working. ... The issue then is the port forwarding on the router. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: XP Firewall blocking Linksys Print Server
    ... When I turn on the the Internet Connection Firewall, ... I added an exception for port 9100. ... > IPX packets that this Linksys print server wants to use. ... protect the machine and set rules for LAN side IP. ...
    (comp.security.firewalls)
  • Re: RDP thru a router
    ... if your testing from another PC on your private LAN use the LAN IP. ... Its possible your ISP is blocking the IIS port, ... Can you test using the normal Remote Desktop client, ie. not the web based method, from both another ... >I have a Linksys router and I wish to enable RDP on a PC behind a router. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Alternative to GoToMyPC?
    ... > Remote Desktop would be your ... > Is there any way to tell what port GoToMyPC was using? ... Shenan Stanley wrote: ... > address and to create a path through the firewall to the pc... ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Can only connect to local RWW, over internet cannot
    ... This if from my working LAN. ... I am testing this tool from my own lan and says 4125 port is closed, ... It has a hardware sonicwall firewall. ... move to the server. ...
    (microsoft.public.windows.server.sbs)

Loading