Discussion Locked

Win98 station can't see network

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a pc on a windows network that is also a netware 4 client. Attempts to browse network neighborhood have no results even after reinstalling a new NIC,netbui,tcpip, and netware protocols. Other pc's on the network can see this station though.

13 replies

by mwdavid

Are you using DHCP or setting the IP address?
Is the NIC setup for 10 MBPS or 100MBPS, Full Duplex or Half?

Try Pinging other machines on the network. If you can Ping, my money is on eht eNetwork card you are using. I have found that the 3COM 3c509 is the best option.

Cheap network cards just don't cut it.

by ntoz

First check to make sure the system is using the proper "WorkGroup" name. It should be the same as your NT domain or the same Workgroup name as the other systems. Second, only load the protocols you need. If your using WINS, make sure your WINS address is correct. Check your subnetmask. If the other stations see it, it might be because of a listing in WINS but the actual station is using the wrong mask.

Pete

by ntoz

Oh one more thing, Ive seen this more then once. Remove all the protocols, Remove Microsoft Networks Client, Remove the Netware Client and Remove File and print Shareing. Make sure you close out the networking windows, this should force a reboot to take effect. Then when you get back in, reload them and keep only the protocols you have standardzied on. Then reboot again. Sometimes these get corrupt and dont give you a lot of information. Somtimes people remove these and then put them back in atthe same time, this doesnt flush them out of the registry.

Pete

by russ werner

Do not trust the display from neighborhood networking.
First try to ping the ip numbers on your network computers. If this works, the try a search for the computer by name.
If both of these work I would try downloading newer drivers for the existing card at www.driversguide.com username=drivers password=all.
If this fails I would purchase a better NIC. The one you are using appears not to be compatable with you hardware/software.

by ecain

Verify the patch cable you are using by placing it on another machine... or using your signal tester, it sounds stupid but I have seen the case where you can send (Tx) but not receive (Rx)... sounds similar to this. An the solution is less expensivethan purchasing a new NIC.

by smbooher

If your netware server is not running tcpip as a standard for networking protocol then go to your client preferences and protocol preferences and change the primary protocol to ipx and bindary. This solves problems with netware servers not being seen by clients. Also make sure you have the latest patch to the NW client you are using.
S. Booher

This discussion is closed to new replies.