RDP + Network issue...

[merlinsghost]

Okay, I did do a search in this forum in regard to Remote Desktop and known issues, but was unable to find any information that deals with my specific issue.

I'll try to keep this short and clear.

Running a domain with Active Directory. No WINS server set up though.

Running Windows 2000 (with SP4) and Windows XP (SP2) (firewall off) on the network.

Here's my issue:

I cannot connect to any of my Windows XP-based boxes using RDP. They all have Remote Assistance/Connection enabled and have users defined that should be able to connect. However, when I try to connect, I get the old "cannot connect to remote computer; make sure remote connection is enabled...blah blah blah".

I can ping these XP machines with any computer on the network (using their name, IP, etc.). I cannot connect to them through Network Neighborhood or an IE window either. But, from any XP machine, I can do all of that, but I am able to connect to and browse Windows 2000-based boxes, which leads me to believe this is an XP issue (basically, I can out-going connectivity from all of my XP boxes, but no in-going connectivity).

I can connect to a 2000-based computer with the XP-based machines, and that computer will then be able to see/contact/connect to the XP-based machine (with RDP, IE, and any other way I choose to connect). But I cannot connect 2000 to XP or XP to XP-based.

I'm kinda stumped.

Any ideas?!

Thanks...

[Ya_know]

I know you said that the firewall is turned off, but ensure that you have Exceptions established and checked for file and print sharing, and remote desktop. Also, under advanced tab of the firewall settings uncheck the local area connection for your network. Some of it may be overkill, but with all those settings tuned just right, I have no problems with RDC.

[merlinsghost]

I know you said that the firewall is turned off, but ensure that you have Exceptions established and checked for file and print sharing, and remote desktop. Also, under advanced tab of the firewall settings uncheck the local area connection for your network. Some of it may be overkill, but with all those settings tuned just right, I have no problems with RDC.

Will do...and let ya know.


It's not just RDP; it's connecting over the network in general.

[merlinsghost]

No luck.

[Ya_know]

Is file and print sharing added, and checkmarked (enabled) under your network properties for the particular LAN config...

[merlinsghost]

Yup, sure is.

I'm just absolutely baffled. :/

[Ya_know]

Well, if you do resolve this issue, Please be sure and expose the answer...will_ya?

[CeeBee]

Terminal Services service running on the remote machine?

[merlinsghost]

Will do, Ya_Know.


Ceebee: The DNS/Domain controller is running Terminal Server, and yes, the XP-based boxes have the Terminal Services service started.

[Thag]

Right-click on "My Computer" -> Properties -> Remote tab -> check the box for "Allow users to connect remotely to this computer"

By default, only administrators can connect this way - or, right below that checkbox hit the "Select Remote Users" button and add the accounts to use to connect.

[merlinsghost]

That was one of the first things I did, Thag.

Thanks for the help though. =]

[shanff]

That was one of the first things I did, Thag.

Thanks for the help though. =]

I'm going to throw in a few...

What kind of network domain are we looking at? Windows 2000 or 2003?

Anyway, look at the security policy of the computers either on the local or the domain level.


Local Policies--> User rights assignment.

check some of the settings to make sure you're not explicitly being denied access. Check the entried dealing with Terminal Services specifically.

Add your username to the Remote Desktop Users group on the local machine if you're not already there.

I just had to deal with a similar issue as far as not being able to log a non-admin user into a Terminal Server. Had to set the user to the proper remote users group so they could log on. Nothing I did on the domain level would get it to work right.

[corturbra]

Have you tried disabling the Firewall and Security Centre services as a temporary measure?

Can you get the user on the XP machine to request remote assistance, can you connect then?

I take it that DNS/WINS is all functioning correctly?

[merlinsghost]

What kind of network domain are we looking at? Windows 2000 or 2003?

Windows Server 2000 domain

Anyway, look at the security policy of the computers either on the local or the domain level.


Local Policies--> User rights assignment.

check some of the settings to make sure you're not explicitly being denied access. Check the entried dealing with Terminal Services specifically.

I'll look that over. Thanks. =)

Add your username to the Remote Desktop Users group on the local machine if you're not already there.

Already done.

I just had to deal with a similar issue as far as not being able to log a non-admin user into a Terminal Server. Had to set the user to the proper remote users group so they could log on. Nothing I did on the domain level would get it to work right.

Thanks for your suggestions. I'll let ya know what happens.

[merlinsghost]

Have you tried disabling the Firewall and Security Centre services as a temporary measure?

Yes, that has been the case from the beginning.

Can you get the user on the XP machine to request remote assistance, can you connect then?

Yes, I can.

I take it that DNS/WINS is all functioning correctly?

As far as I can tell, yes, though we don't have a WINS server.