suddenly can't remote desktop to one of 13 servers
I do a ton of work remotely on our 13 servers and always use remote desktop to access them. About 10 days ago I put security patches on all of them and now I can't remote back into one of the servers. It is a domain controller, but not the primary and I can still remote to the primary as well the other domain controller. I still have the option checked for remote access. I had this happen once before and doing a 2nd restart fixed the problem. That hasn't worked. I don't know what else to check - espeically since I can still remote to the other 12 servers.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
NetAdmin2436
....also try checking the firewall settings on the troubled DC. I'd disable the firewall completely during troubleshooting.
ASKER
I get an error that remote desktop disconnected - the error says: This computer can't coonect to the remote computer. Remote connections might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are preventing your connections. Please try connecting again later.
There are no messages in the event log and I have tried clearing the checkbox, etc.
There are no messages in the event log and I have tried clearing the checkbox, etc.
ASKER
We do not have Windows firewall started on our servers. We use an appliance instead.
Is terminal services running?
ASKER
Yup - terminal services is running.
Are you connecting by Name or by IP? If you're using the name, can you ping it by name? If not, try the IP, it may be a DNS issue.
ASKER
I've tried connecting by name and by IP address. Neither work. But I can ping and arp both.
Do you have the ATI Catalyst suite installed on the server? I saw something about an issue with that. May want to consider uninstalling any unnecessary video stuff.
You could try mstsc /v:servername /console see if that makes a difference, I doubt it though.
You could try mstsc /v:servername /console see if that makes a difference, I doubt it though.
ASKER
No we don't have an ATI catalyst suite installed.
I read something about servers with 2 network cards have some kind of issue. But it seemed to be a couple of years old, so I didn't follow through on it. I wonder if it has to do with some patch I applied - but I put pretty much the same pathces on all machines.
I read something about servers with 2 network cards have some kind of issue. But it seemed to be a couple of years old, so I didn't follow through on it. I wonder if it has to do with some patch I applied - but I put pretty much the same pathces on all machines.
Ah...are both the NICs in use? If not, is the one that is not in use disabled?
A domain controller / DNS server should only have one NIC / IP. Otherwise it can get confused. Additionally, if you don't disable an unused NIC, it could pick up an APIPA address which can even further confuse things.
If the NICs are teamed or set up for failover, that's one thing, but if they have different IPs or one isn't used, that has to be addressed.
A domain controller / DNS server should only have one NIC / IP. Otherwise it can get confused. Additionally, if you don't disable an unused NIC, it could pick up an APIPA address which can even further confuse things.
If the NICs are teamed or set up for failover, that's one thing, but if they have different IPs or one isn't used, that has to be addressed.
ASKER
This is on an HP server and yes they are teamed up and have 1 IP address. Its worked for the 9 months this server has been in production - that's the confusing part.
....just an idea here. Have you tried rebooting the switch? Maybe something went funky with the switch port. Or if it's a managed port, maybe you can log into the switch and see any errors on that port.
Any errors in the HP NIC management?
ASKER
It turns out this simple solution finally worked.