We have a network with 2 IP-ranges and in Mixed mode: W2K en WNT4 both DC Active Directory is set up, DNS and WINS are comming from W2K (P)DC and DHCP from WNT4 (BDC)
All the servers can see eachother.
This is occurs on W2K Workstations (Pro SP2) and the W9x clients do not have this problem !!! When we enter on a W2K workstation "net view SERVERNAME" it returns "there are no entries" When we enter on the same workstation "net view SERVERIPADDRESS" it returns a list of shares on that server
Now the weird thing. When we enter on that same WS "net view SERVERNAME.DOMAIN.COM" it also returns the server shares.
The problem is that the printer shares are on the WNT4 server and as a cause (probably) of the problem occuring above, the workstations can not see those printer shares!!!
Start -> Control Panels -> Network -> Protocols -> TCP/IP -> Properties -> DNS
(I have a german language NT4 system running here at the moment, so the terminology may be slightly different, and the path to the relevant dialog may be different on W2k as well.) On the DNS settings page, there are two lists for slightly different varieties of "search sequence". Probably in the first one, you should add your "domain.com". If that doesn't fix the problem, try adding it to the second list instead.
It's important to understand that "servername" alone is not sufficient to determine a host IP address per DNS. the DNS server needs a fully qualified domain name (FQDN) like "servername.domain.com" for the translation. The search sequence lists of the client are a convenience feature, so that you can use unqualified host names from within the domains listed there. It will then simply combine those names with each entry in the list, and ask the DNS server to resolve "host.domain1.com", "host.domain2.com", etc. in the sequence specified there, until it either gets a positive answer or the list is exhausted. It is possible that the W9x client uses the domain specified for the local system as a default entry into that list, which may be even more convenient, but is probably not standards conformant.