Re: Windows 2003 RDP will not work with WAN but port 3389 is listening
- From: Cl‡audio Rodrigues <CR@xxxxxxxxxxxxxxxxxxx>
- Date: Tue, 10 Nov 2009 12:42:14 -0500
In_the_dark wrote:
This questions has been asked before but having searched I believeCheck the router configuration. You must have a port forwarding rule from the outside to the TS internal IP on port 3389. Do you have that?
mine is a bit different.
Windows 2003 Server with SP 2 and port 339879 running and will allow
RD connections from LAN only. Wan connections fail with that "Can't
connect .... " message. This has only been apparent for the last week
and had previously worked fine. There is no evidence on the server
that anything has changed during that time. A second machine on the
same LAN will allow RD connections from the WAN. Windows Firewall
allows the RDP to pass. The router a Netgear DG834G allows one of the
packets through but not the other. At this stage I have tried
everything from changing the ports to changing cables, resetting the
router and hassling the ISP. I would very much appreciate pointers or
some links to possible reasons for this as I am stumped.
--
Claudio Rodrigues
CEO, WTSLabs Inc.
http://www.wtslabs.com
"WebTS: TSWeb the way it should have been done since day one"
Citrix CTP
Provision Networks VIP
Make sure you download our free guide about Terminal Services.
An A to Z guide, explaining everything, from setting it up to enabling
group policies. A must read and again, completely free.
.
- References:
- Windows 2003 RDP will not work with WAN but port 3389 is listening
- From: In_the_dark
- Windows 2003 RDP will not work with WAN but port 3389 is listening
- Prev by Date: Re: Version
- Next by Date: Re: 70 permission denied
- Previous by thread: Re: Windows 2003 RDP will not work with WAN but port 3389 is listening
- Next by thread: Users access denied installing network printers
- Index(es):
Relevant Pages
|
