tsadmin not displaying Windows 2003 servers

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello:

I have an large environment with Windows 2000 and Windows 2003 servers along with a NT PDC and BDC. When using tsadmin from the 2000 servers, I can view all of the other servers EXCEPT for the 2003 servers. I can see all of the servers from the 2003 tsadmin utility. I can connect to all of the 2003 servers by netbios name with remote desktop, they just aren't displaying in tsadmin. The 2003 servers are all on the same subnet as the other 2000 servers. Is there some kind of security steting preventing this?? Thanks in advance for any help!!

-Derek
 
Do you happen to have any security settings on the network
card of the 2003 servers that might be causing this?

The Windows 2000 tsadmin.exe utility (I think) sends out
broadcasts to all your servers to detect which servers are
running terminal services. You might want to try running
a packet trace to see if the packets aren't making it
correctly. Better yet, try hooking a crossover cable from
you server to another 2000 server and seeing if the
tsadmin utility can see the other server. Then do the
same to a 2003 server. What happens then?

-M
-----Original Message-----
Hello:

I have an large environment with Windows 2000 and Windows
Click to expand...
2003 servers along with a NT PDC and BDC. When using
tsadmin from the 2000 servers, I can view all of the other
servers EXCEPT for the 2003 servers. I can see all of the
servers from the 2003 tsadmin utility. I can connect to
all of the 2003 servers by netbios name with remote
desktop, they just aren't displaying in tsadmin. The 2003
servers are all on the same subnet as the other 2000
servers. Is there some kind of security steting
preventing this?? Thanks in advance for any help!!
 
Hi Matt

If I do a nbtstat -a VIRT01 (a W2K3 server) from a W2K server and it returns the netbios name. I can also ping VIRT01. Unfortunately, they are production systems so I won't be able to hook up a crossover cable to them. Do you know, that because W2k uses RDP 5.0 and W2K3 uses RDP 5.2, would this cause a problem? Thanks for your help

-Derek
 
The fact that they are running different versions of RDP
shouldn't matter, since both those versions should respond
to the same broadcasts. Do you think you might be able to
hook a crossover cable between the two computers sometime
over the weekend or during some downtime?

-M
-----Original Message-----
Hi Matt,

If I do a nbtstat -a VIRT01 (a W2K3 server) from a W2K
Click to expand...
server and it returns the netbios name. I can also ping
VIRT01. Unfortunately, they are production systems so I
won't be able to hook up a crossover cable to them. Do
you know, that because W2k uses RDP 5.0 and W2K3 uses RDP
5.2, would this cause a problem? Thanks for your help.
 
Back
Top