Earlier today I was connecting to my WIN2000 server just fine. I gained a little courage and decided to tinker around now I cannot log in at all with my Terminal Services. I contacted tech support who can connect to my server just fine using Terminal Services so I assume the problem is me. Here's the problem... I try to connect and receive the following error:
Terminal Services client disconnected
The Terminal server has ended the connection
I search my event logs for clues and found this:
Unable to contact a DHCP server. The Automatic Private IP Address 169.xxx.xx.xx will be assigned to dial-in clients. Clients may be unable to access resources on the network.
The only thing I did today was go into Control Panel > System > Network Identification > Network ID which brought up a wizard for setting up connection for a private computer or one on a business network. After I fooled around with this wizard I lost ability to connect to my WIN2000 server using Terminal Services. (I am still able to ping and tracert using the ip).
THANKS!!!
Terminal Services client disconnected
The Terminal server has ended the connection
I search my event logs for clues and found this:
Unable to contact a DHCP server. The Automatic Private IP Address 169.xxx.xx.xx will be assigned to dial-in clients. Clients may be unable to access resources on the network.
The only thing I did today was go into Control Panel > System > Network Identification > Network ID which brought up a wizard for setting up connection for a private computer or one on a business network. After I fooled around with this wizard I lost ability to connect to my WIN2000 server using Terminal Services. (I am still able to ping and tracert using the ip).
THANKS!!!
