Two Win2k computers on same LAN; 1 can telnet, 1 cannot, Please advise 1

[ftoddt]

Hi,
I had this posted on the Windows 2000 forum and it was suggested that I move it here so here it is.

I have 2 Win-2k computers on the same Win-2k LAN. One can telnet, the other cannot. Users are the same. Have tried with command prompt telnet and only one can connect. Have compared running services on both and they appear the same. Both connect thru an ISA server to the external router and both configured on the NIC card the same. Both can ping the telnet server but only one can telnet connect. Have booted to safe mode with networking and still cannot cmd telnet. Is there a personal firewall or port security setting that I am missing on one and not the other. I don't know what else to look for. Thanks for your time in reading this.
Todd

P.S.

Between the one pc that can telnet and the one that cannot, I have switched eithernet cables, have switched IP addresses using static IPs, and have tried in safemode with networking with no improvements.
What I haven't told you is that I have had DNS problems with a slow XP logon to a Windows 2000 Server that I could never solve. I recently did a DNS reinstall and everything works except, I cannot nslookup satisfactory with any computer presently on the domain. All win-2k clients can presently log onto the domain with no lag, some xp clients lag about 10-20 min, all clients can access our own server email, can ping all other computers and can see all other computers in the domain under network neighborhood.

What troubles me besides DNS is from what I understand, telnet is very very basic and should not have much to do with DNS. I was told that telnet relies primariy on baud rate and ability to see telnet server(I can ping it but cannot connect). Firewall seems out since some can telnet and some cannot. One consistancy so far is that the computers that can telnet are older ones in our domain while these newly configured ones cannot. Swithing IPs of the older to the newer made no difference.
I am very very new at this and unfortunately do this as a sideline to help a local school district. School is almost out and am considering starting over on the whole system. I am about the fourth semi-IT and as we know everybody does it different. I am just trying to band-aide it as best I can.
All of you at this site have been most kind and helpful to me. I could not have lasted these 18 months without you.
Thank You

 

[minxca]

1. Install netmon or Ethereal and try telnet again.
2. Cabling proble
Have to try to telnet with IP Address?
3. Check the telnet port in "services" file Under winnt\system32\driver\etc.

About your DNS, nslookup doesn't resolve internal name:
1. Are you sure your client use your internal DNS?
2. Do you allow dynamic update? Check your DNS entries.Can you ping with FQDN?

If the login process take a long time:
1. Install BootVis from Microsoft. I think you can't download from MS site anymore, google it. Run this to analize the login process.
2. Cabling, move the pc to another location or unplugg the cable.

 

[ftoddt]

Winoto,
Thank You so much for all the wonderful things for me to try. I will have to check out netmon and Ethereal because I don't know what they are.
I can telnet using Ip on some pc's and not on others. When I look in the "Sevices" file, I just need to see that that port is in there, correct? I looked at that file on a computer here at my other job and it just shows the many ports but I cannot tell if there is an active or not active in that file..??
I believe that clients are using the internal DNS in order to log in to the domain or when I join a computer to the domain. Routing and internal mail seem to work quite well as long as mail coming in or out. I do have forwarders on the ISA and exchange to secure outside dns servers belong to the school system but not part of our LAN. I did check allow dymanic update but will check again to make sure.
I think I found Bootvis a while back and for some reason it did not work for me but will try again. Maybe I could not find it. I will research and find it again.
I did change the cables between the working telnet and the non working telnet with no change.
Thanks again for all your help. You have given me lots to look at and I will keep you posted on the results. I really appreciate your time.
Todd

 

[ftoddt]

Problem Solved. ISA Server problem in that the computers not working did not have Microsoft Firewall Client installed. Once that was done, telnet worked just fine.
Thanks to All
Todd