• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1040
  • Last Modified:

NT4 workstations will not net view server or net use share names. System error 53. FQDN or IP works fine.

We have a mixed workstation environment.  NT4, 2000, XP.  We have two domains, both with NT4 PDC's and BDC's.  We do not use wins, since our network is all one logical segment.  We set the workstation to use NetBIOS over TCP/IP.  We have no problems with the 2000, and XP clients.  However on any NT4 client, we are seeing that they cannot net view or connect to network resources.  When we do a net view to a hostname, we get a system error 53.  If we use the ip address or the fully qualified name, (\\hostname.xxx.com), it works.  But if we ping the hostname, it is resolved by DNS just fine.  We have tried forcing the node type to H, and tried it with node type B, with no luck.  The problem is also strange in that it is not happening on all servers we try to connect to, even though some that work are identically configured to some that don't.  We have also seen some just start working for no reason at all.  This problem is also causing the NT4 clients to have to logon with cached account information, because the pdc is one of the machines having the problem.  Our current workaround is to install NetBEUI on the workstations, but we would eventually like it to work with only IP.
0
pshirmey
Asked:
pshirmey
2 Solutions
 
daJmanCommented:
>But if we ping the hostname, it is resolved by DNS just fine
You have DNS on the LAN?

If your using DNS you dont need NetBIOS over TCP/IP. Just make sure your NT Workstations have only your internal DNS server's IP listed. Your DNS server should be configured to look past the router for domain names it is not authouritive for.

If you're not using DNS, the inconsistancies your seeing is probably the PC caching names. Running "nbtstat -c" from the command line will tell you the names that PC knows. Try that on all the PC's that are having connections issues and you'll get some insight on why some clients can see some servers.

>Our current workaround is to install NetBEUI on the workstations, but we would eventually like it to work with only IP
If you want to go only IP, prior to Active Directory, WINS is the way. If you dont want WINS, the other reliable way is to use LMHOSTS files. This gets quite tedious with many PC's.

Perhaps one of the 2k or Xp boxes are assuming the master browser role.


More help:

Troubleshooting the Microsoft Computer Browser Service
http://support.microsoft.com/default.aspx?scid=kb;en-us;188305&Product=nts40

Whitepaper: Microsoft Windows NT Browser
http://www.microsoft.com/ntserver/techresources/commnet/browser/ntbrowser.asp

Domain Browsing with TCP/IP and LMHOSTS Files
http://support.microsoft.com/default.aspx?scid=kb;EN-US;150800

Information on Browser Operation
http://support.microsoft.com/default.aspx?scid=kb;EN-US;102878

NET USE Attempt Across Domains Fails Without Name Resolution
http://support.microsoft.com/default.aspx?scid=kb;en-us;193836&Product=ntw40

0
 
JammyPakCommented:
I wouldn't disable NetBIOS over TCP/IP, but I would install a WINS server.

Logging into a domain does not use the browser service or the master browser. It either does a WINS query, a broadcast, or a LMHOST lookup (depending on the node type, the order will change).

Since you don't likely have all DCs hardcoded in everyone's LMHOSTS file, and you don't have WINS, that means that you're relying on broadcasts for the clients to find a domain controller.

My guess is that you will find things to be much more stable and reliable if you install a WINS server on one of your servers (could be the DC, doesn't matter) and then set a WINS server address on all clients (hopefully you're using DHCP, cause that makes it easy).

HTH,
JP
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now