down (65545)

[ritchie]

In the terminal services manager this is where RDP-TCP
(listener) is supposed to be. Any one know why and how I
can fix it ?

 

[Guest]

Before I do any research, did you try bouncing the server to see if the problem goes away, then check the event logs to see if there are any error messages related to TS

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co


----- ritchie wrote: ----

In the terminal services manager this is where RDP-TCP
(listener) is supposed to be. Any one know why and how I
can fix it

 

[ritchie]

Yes several times. I uninstalled TS and reinstalled it
also. same thing.I had did an inplace upgrade to change
mother boards. The disk I used was win2k server w/sp4.
IEvery thing else works including exchange2k.

-----Original Message-----
Before I do any research, did you try bouncing the server

to see if the problem goes away, then check the event logs
to see if there are any error messages related to TS?

 

[ritchie]

The inplace upgrade put another nic in call nic #2. I
checked the manager and it was pointing to all interfaces
so I changed it to nic #2 but I saw the old nic is still
in there. I can't figure out how to get it out of there

-----Original Message-----
Check the RDP-Tcp Connection in the Terminal Services

configuration to make sure it isn't trying to use a NIC
that no longer exists.

 

[Guest]

Go to Device Manager -> View -> Hidden Devices -> Delete

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- ritchie wrote: ----

The inplace upgrade put another nic in call nic #2. I
checked the manager and it was pointing to all interfaces
so I changed it to nic #2 but I saw the old nic is still
in there. I can't figure out how to get it out of ther

-----Original Message----
Check the RDP-Tcp Connection in the Terminal Services

configuration to make sure it isn't trying to use a NIC
that no longer exists

 

[ritchie]

The old nic is not in device manager->hidden devices

 

[Ritchie]

We just did all the post hotfixes hopeing that would solve
something but it didn't. there is a non existant nic
listed in the network adapters in terminal server
configuration. That is the only place it is listed that I
can tell. We set it to just use the real one but that
doesnt seem to make a difference either. I noticed the
down (65538) it think it goes back on reboot.