Discussion Locked

Server is not visible in Win98 network

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Running a Win98 peer-to-peer network. Server also has Win98. The server is only used to share files.
Server IP is 192.168.0.1
Client IP is 192.168.0.8

I can ping each way with success.

11 replies

by ann777

Both the "server" and the client are Win98? If yes, then install the MS NetBEUI protocol to both computers. Also enable the "shares" you need and make sure that both computers are in the same domain or workgroup.

by tjc

make sure that "file and printer" sharing are setup in the properties of "Network Neighborhood" also

by phil.hall

Make sure both machines are on the same domain and workgroup, as defined in the TCP/IP properties page.

Additionally, make sure the subnet masks are identical.

by carny

Thanks for the help......This fixed the problem. Of course I feels stupid missing it. Thanks again.

by larryny1

Try a few of these things as well.

1. Under Network Neighborhood Properties make sure Client for Microsoft Networks is there. Logon to NT domain should not be selected.
2. TCP/IP Properties, Bindings - check ms client and file and printer sharing. DNS - make sure its disabled. IP Address - Obtain an IP Address automatically.
3. NIC Card should be bound to the correct TCP/IP Protocol
4. Try putting both machines into the same workgroup.

Best of Luck
Larry

by spfaff

I'm assuming:
-You have static IP's set
-The Workgroup is set the same for both
-You have something shared on the server
-File sharing is enabled on the server
-subnet masks match (you can ping successfully)
-Your network stack is simple
Client for microsoft networks
TCP/IP
File and Printer Sharing for Microsoft Networks
-You can't see the server in Network neighborhood
on the client.

It can take a while for the Browsetable to update
in Windows Pier to Pier networks,
Try this on the Client-
Start:Find:Computer and enter the Servers
computername, It Should find it. Now if you go into
the clients Network Neighborhood, the Server should
be visible.

A reasonable workaround for this is to Set
BrowseMaster=ENABLED in the Server and DISABLED in
the Client. This can be found in the Properties
page of File and Print sharing for Microsoft
networks in the Network Configuration panel.
What this does is to make the Server maintain the
Browse table.

Hope this solves your problem.
Steve

This discussion is closed to new replies.