J
J. Knapp
Here's one that has me scratching my head. One of the clients on the local
LAN can't connect to one of our terminal servers. he can connect to any
other TS in the domain, but not a specific one.
There are packets being passed between the two machines, but the server
must reject something (I'm not all that skilled in reading the packets from
Network Monitor) becuase after a dozen packets, it just fails, and he gets
the usual "Can't connect... three things" error box.
He's running Win2K Pro with the latest RDP client. The other similarly
configured machines on the network have no trouble logging on to that TS.
I've reinstalled the client a few times, and it doesn't seem to do any
good.
Anywhere else I should look?
LAN can't connect to one of our terminal servers. he can connect to any
other TS in the domain, but not a specific one.
There are packets being passed between the two machines, but the server
must reject something (I'm not all that skilled in reading the packets from
Network Monitor) becuase after a dozen packets, it just fails, and he gets
the usual "Can't connect... three things" error box.
He's running Win2K Pro with the latest RDP client. The other similarly
configured machines on the network have no trouble logging on to that TS.
I've reinstalled the client a few times, and it doesn't seem to do any
good.
Anywhere else I should look?