Hi, I have networked 2 98se pcs and 1 win2kpro pc and used to be share drives well, but recently there is one 98 pc(A) can only see the other pcs but any attempt to access the shared drives on pcs results in a hang-up of machine. From win2kpro pc and the other 98 pc(B) there is no problem to access the shared drives and printer on 98 pc(A). The win2kpro and 98 pc(B) have no problem to share drives each other. File and Printing Sharing is checked on all pcs. Networkcard on 98 pc(A) is '3Com OfficeConnect NIC (3CSOHO100-TX)', on win2kpro is '3Com EtherLink 10/100 Mbps EtherLink PCIs (3C90x family)' and on 98 pc(B) is Linksys NIC... I can't figure out why? Please help, thanks.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Network neigborhood problem
- Thread starter lweng
- Start date
Have you changed network cards on (A) or reconfigured it recently? Any other recent changes on (A)?
Do you have more than one protocol in use - say TCP/IP and Netbeui?
Is it possible that you have a default protocol declared on one machine different than (or none declared for) the others ('set this protocol to be the default protocol' is checked off in advanced tab of network properties for a given protocol)?
Netbeui might enable you to browse but using TCP/IP for default access with invalid configuration on one machine might account for the results indicted by you.
Do you have more than one protocol in use - say TCP/IP and Netbeui?
Is it possible that you have a default protocol declared on one machine different than (or none declared for) the others ('set this protocol to be the default protocol' is checked off in advanced tab of network properties for a given protocol)?
Netbeui might enable you to browse but using TCP/IP for default access with invalid configuration on one machine might account for the results indicted by you.
You can also get problems like this using cards from different manufacturers. There are some subtle timing differences that lead to cards disappearing. Ed Fair
efair@atlnet.com
Any advice I give is my best judgement based on my interpretation of the facts you supply.
Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.
efair@atlnet.com
Any advice I give is my best judgement based on my interpretation of the facts you supply.
Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.
It might be a good idea to check the network card in all 3 pc's to make sure they are firmly seated in their slots on the respective motherboards.
Are you using a hub. If so you should look at the modular plugs entering the hub for damage or if one is not pushed in far enough.
Examine the network cable paths in case a piece of furniture was recently moved and pinched a cable into partial disability.
Make sure all networked machines have the same workgroup ID.
Are you using a hub. If so you should look at the modular plugs entering the hub for damage or if one is not pushed in far enough.
Examine the network cable paths in case a piece of furniture was recently moved and pinched a cable into partial disability.
Make sure all networked machines have the same workgroup ID.
On 98pc(A), rebuild the network stack. Uninstall Client for MS Networks, which should remove all the protocols and File and Print Sharing. Reboot then readd the components and protocols that the other networked PC's are using. Reboot again. This almost always works for me.
- Thread starter
- #6
Thanks for the replies, I tried all, replace same brand netwotk card, uninstall Client for MS Networks, reboot then readd the components, and changed the network line..., still fails. Looks the problem is in the pc, is anything wrong with bios? Can't figure out why? Thanks
- Status