Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.
CAN'T SEE DOMAIN
Name: ARPRINCE Date: February 5, 2002 at 11:13:35 Pacific
Comment:
I have an NT4 svr (SP5) and WIN98 client. When both are on the same network/segment, the client can see the domain and can log into it. However, when we place the NT server on a different network with a router in between, the client can't see the domain.
TCP/IP is enabled and both can ping one another. I have CLIENT FOR MS NETWORKs enabled in WIN98 so it looks for the Domain when booted up.
Name: Tony Munday Date: February 5, 2002 at 13:09:38 Pacific
Reply:
Don't know of this will help...
If you are talking see in the sense of Network Neighborhood then protocols could be the problem. NETBUI is generally what makes the machines appear, but it is not a routable protocol. NETBIOS over TCP/IP would fix that.
0
Response Number 2
Name: zoolander Date: February 6, 2002 at 16:25:15 Pacific
Reply:
Better yet, install WINS services on the Win NT Server, and on the Windows 98 machine, set the WINS server address to the Win NT Server. Now you can move the NT Server to any segment you want and the 98 machine should be able to find it. So all you need is:
1) TCP/IP Protocol 2) WINS Server service on NT Server 3) WINS address set to NT Server on 98 client
0
Response Number 3
Name: Ben Date: March 14, 2002 at 23:30:49 Pacific
Reply:
I am having almost the same problem. But only diff is that both the systems are NT4. One is a PDC and the other is a member server on a stand alone server. The PDC is running WINS but still am unable to browse network. But the nslookup is able the resolve the pdc name, able to ping and even map the drives using IP but just cannot browse that domain to which the PDC belongs to from the member server. Any help would be greatly appreciated.
0
Response Number 4
Name: Ben Date: March 14, 2002 at 23:32:45 Pacific
Reply:
sorry...should read member server on another domain.
Summary: I'll bet it is a WINS issue ! :) Whenever you can't see a domain controller, 9 out of 8 times it is a WINS issue. Go to TCP/IP and make sure you have the entry for the Primary WINS server entered. Don...
Summary: Hi guys I'm dialing into a private network, using a normal analogue phone line. It dials into a Cisco remote access server, which verfies my username and password by comparing it to my Windows NT doma...
Summary: Hi Fred, The NIC error you are seeing may not be produced by the NIC itself. In our Domain(s) of 45 NT Servers I came across similar type errors. Often the root causes were bad NIC's, sometimes th...
0 
