Re: Port 3389 where and how and more
From: Bill Sanderson (Bill_Sanderson_at_msn.com.plugh.org)
Date: 02/03/04
- Next message: Bill Sanderson: "Re: Remote desktop to Server 2000 at work"
- Previous message: Danijel Tkalcec: "ANN: Remote Office 2.04 - using GDI Hooks"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 3 Feb 2004 15:45:43 -0500
Nat's pass all traffic outbound, but block unsolicited traffic inbound.
Connecting outbound doesn't mean you will be able to connect inbound without
setting the router to allow the inbound connection. Take a look at the html
admin for the router--its either called port forwarding or virtual servers.
"rotund" <rotund.10rwui@mail.mcse.ms> wrote in message
news:rotund.10rwui@mail.mcse.ms...
>
> I am in the same boat as you are. I cannot connect to my home machine
> running XP Pro SP1 from work, but I can successfully use Remote Desktop
> from my home machine to my machine at the office. I have removed Zone
> Alarm Pro, turned off MS Internet Connection Firewall ( I am not
> comfortable with that but there it is) and traffic on 3389 is set to
> pass through the D-Link dsl router. So far nothing I have tried will
> work. I know that the router is passing traffic on port 3389 since I
> can RDC to the office from this machine. Any suggestions?
>
> John V
>
>
> rotund
> ------------------------------------------------------------------------
> Posted via http://www.mcse.ms
> ------------------------------------------------------------------------
> View this thread: http://www.mcse.ms/message237980.html
>
>
>
- Next message: Bill Sanderson: "Re: Remote desktop to Server 2000 at work"
- Previous message: Danijel Tkalcec: "ANN: Remote Office 2.04 - using GDI Hooks"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
