Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Remote Desktop Connection

Status
Not open for further replies.

logicacmg000

Technical User
Sep 30, 2004
75
US
I am unable to connect to a Win 2003 w/SP1 machine just installed new on our development subnet. This machine is on a different subnet than the users. However, other machines on this subnet can be accessed by our users.
I've configured Net Meeting to run for now but I cannot figure out what's the missing piece here.

Are there any specific services that need to be up? There is not firewall rule blocking this. Also other machines on this subnet can be accessed via RDC.

Any helpful hints are greatly appreciated.
Thanks.
 
Sounds like a IP Misconfiguration. Check the IP address, subnet mask and gateway of the problem server.
Depending how your users are trying to connect to the server it could also be a name resolution problem. Make sure the new servers DNS and WINS configurations are OK. From the user subnet if you can ping the server by IP and cant ping it by name - name resolution issues.
 
If you installed W2K3 with SP1 integrated into the install (ie you didn't load the SP post-install), then the integrated windows firewall will be enabled. You probably can't even ping the server. Disable the firewall feature (There's a control panel for it) and try again.

Also, you can try port scanning the box and see if port 3389TCP is available (RDP).

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top