Computing.Net > Forums > Windows Server 2003 > Remote Desktop in 2003 Enterprise

Computing.Net: Over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to sign up now, it's free!

Remote Desktop in 2003 Enterprise

Reply to Message Icon

Original Message
Name: TechHead
Date: September 11, 2003 at 06:41:58 Pacific
Subject: Remote Desktop in 2003 Enterprise
OS: Server 2003 Enterprise
CPU/Ram: 1.67 MHz / 384 MB RAM
Comment:

My setup:
AT HOME:
-Linksys WRT54G router connected to a bellsouth ADSL modem, port 4899 TCP-UDP is forwareded to the Server. Router IP is 192.168.1.1

-Server 2003 Enterprise, connected to the router, using local IP - 192.168.1.100 subnet mask 255.255.255.0, gateway is the linksys 192.168.1.1

-2 Laptops wireless connection to the router, Local IPs 192.168.1.101 and 192.168.1.102 subnet 255.255.255.0, gateway is the linksys 192.168.1.1

AT WORK:
-My workstation is connected to the corporate LAN

I can use my corporate VPN to connect to the work LAN. The tunnel drops me right outside of the corporated firewalls. I can use this to get on the LAN, then use remote administrator v2.1 to log onto the desktop of my workstation from any computer in my home LAN. I am trying to go the other way now. I want to connect from my workstation at work to my server at home. I have the ports for Remote Administrator 4899, the port for Remote Desktop 3389, and port 80 for my webserver forwarded from the linksys to the server. The only thing that works correctly is port 80. I can access my web site from anywhere, but when i try to run remote desktop it times out. When I try to run remote administrator, I get the "connection IO error, connection may be closed due to IP filter settings on the remote side"

I am not using an IP filter on the server. Microsoft has done well with locking Server 2003 down out of the box, so maybe I am missing some esoteric checkbox somewhere??? Any ideas would be very welcome.



Report Offensive Message For Removal


Response Number 1
Name: blin
Date: September 11, 2003 at 06:51:46 Pacific
Reply: (edit)

what kind firewall do you have at work? if you have cisco pix with old version, you may need to configure pix and let inside computer connect to the home. also use telnet to checl the open port.

For more tips or information, go to http://www.ChicagoTech.net

Robert, MS-MVP/MCSE and CNE
Windows & Network Support, Tips and FAQs on
http://www.ChicagoTech.net


Report Offensive Follow Up For Removal

Response Number 2
Name: TechHead
Date: September 11, 2003 at 06:57:52 Pacific
Reply: (edit)

Hey Robert thanks for the reply,

we use sidewinders here. Ports don't seem to be an issue. A co-worker can remote desktop to his server at home using the IP with ports forwarded through a linksys router with no problem.


Report Offensive Follow Up For Removal

Response Number 3
Name: nav27
Date: October 15, 2003 at 04:52:22 Pacific
Reply: (edit)

Basically Linksys Virtaul Server should be configued, saved try a reboot.

I have a SMC router & it works.

Private IP Private Port Type Public
1. 192. 168. 2.1 80 TCP 80
2. 192. 168. 2.1 3389 TCP 3389

Download the from MICROSOFT Website TSWEB; install it on your host PC & you can browse your Server via IE!



Report Offensive Follow Up For Removal

Response Number 4
Name: sziszi
Date: October 27, 2003 at 02:28:14 Pacific
Reply: (edit)

Hi.I have the same problem, but with a little difference.I try to reach the Windows 2003 Terminal server over a Linux firewall.
I've been forwarded the port 3389 to my internal IP adress 192.168.1.2 ad still unable to connect.I tried to install a Windows XP Pro on the internal machine and it works with Remote desktop connection from outside, with the same firewall rules.
Can anyone help me with this thing?
Thanks!


Report Offensive Follow Up For Removal







Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home








Do you own an iPhone?

Yes
No, but soon
No


View Results

Poll Finishes In 7 Days.
Discuss in The Lounge
Poll History




Data Recovery Software