Why can't I see the others on my network?

[themadmonk]

I have two computers connected on a network. One is Windows 98 and the other is Windows 2000. The Windows 98 computer can see the Windows 2000 computer. The Windows 2000 cannot see the Windows 98. The Windows 98 is also used as a connection sharing computer (server), and the Windows 2000 (client) can surf the net. So I know the connection to both comps is good, just cannot see the Windows 98 comp.
What could be causing this problem?

 

[Fardringle]

Two fairly obvious questions, but easy to miss:

Does the Win2K system have Client for Microsoft Networks installed? If not, that's why it can't browse your network.

Does the Win98 system have File and Printer Sharing for Microsoft Networks installed? If not, that's why the Win2K machine can't see it...


There are other things to try, but those two are the first things to check, especially since you've already established that the connection itself is good.

 

[themadmonk]

Yes File and Printer Sharing is installed on both machines.

 

[obenton]

See if the win98 machine comes up when you do Search /Computer. If it does, you're OK. The NetN'hood delay is common. Another possibility is that a firewall setting is blocking the connection.

 

[themadmonk]

Did the search nothing, had zone alarm but set local internet settings to minimum.

 

[obenton]

You might try putting in Netbeui as the default LAN protocol.

 

[Maximus1]

I've heard that Netbeui does help when networking Win2k and Win98. I would definitely give that a try.

 

[themadmonk]

Tried NetBEUI, nothing. This is really pissing me off because I could used to see the other computers before and now it just up and went out.

 

[RossGr]

You did share the hard drive on the Win98 machine didn't you?

Right click on the harddrive in Mycomputer and select sharing. follow you nose.

 

[themadmonk]

All on the Win98 machine is shared.

 

[ETLA]

I have the same problem after setting up my Linksys router finally!!! and we both can get online me running Win2k and other comp running 98SE. we can see each other but we CAN NOT access to each other's comp! I did set up file and print sharing......

 

[Orbius]

This is fairly common, make sure the file/print sharing checkboxes are still checked. They spontaneously unchecked on my machine before. In Start-->Control Panel-->Networks make sure that Client for Microsoft Networks and not Microsoft Family logon is selected as your Primary Network Logon. After you change it look at the file/print sharing checkboxes again.

Also when your PC boots up be sure to enter a password, I use my initials.

 

[themadmonk]

If I install anything more having to do with networks on my computer I will need a second monitor to hold the listing. I have installed every protocol, client, device, etc. ever produced. Now I am wondering if it has anything to do with Win2K Services.

 

[TerreApart]

Have you seen this?

w2k peer to peer

 

[spidey07]

Don't feel frustrated this is a common occurance with windows.

I'll post the basic "spidey's winblows browse list cheat sheet". First off make sure all netbios names (network control panel--->identication) are unique and less than 14 characters alphnumeric only with maybe spaces...yeah spaces are supported, don't use them.

1) If using multiple protocols then deinstall everyting except IP. Binding orders can confuse windows.

2) Ping the other machines by IP. If succesful then IP is working well.

3) Under command prompt type "net view \\COMPUTERNAME" where comuter name is computer name. If you can do this then good, netbios over IP name resolution is working for individual machines. You should be able to open up the shares on the remote machine by doing start-run--->\\COMPUTERNAME. If not then start from the beginning of the post. Windows depends heavily on COMPUTERNAME.

4) Now try to get what is called a "browse list". This is a list of domains/computernames that shows up when you open "network neighborhood". (a.k.a SEE other computers). Best way is to type in "net view //WORKGROUP:workgroup" By doing this you are broadcasting a "get subnet master browser" announcement. If nobody responds, like maybe they are in sleep power mode then you will get nothing. If a computer actually responds, that computer will tell you who the subnet master broswer is. The subnet master browser is responsible for keeping a list of all computer names (aka netbios names) and this is the machine you ask for a listing of domains/computers. Most problems stem from your machine not figuring out who the subnet master broser is, therefor it is unable to request a browse list.

5) The above 4 steps pertain to the WORKSTATION service of winsucks. Next to look at is the "SERVER" service of "ohh my god they call this an operating system". If you are not sharing files or printers then you don't have a server service running. without a server service you will not announce yourself the the BROWSELIST. I'm not say you won't register you computer name with the naming service because you will, BUT you will not announce yourself. Therefore you are not part of the BROWSELIST. Bottom line...if you don't have anything to offer other windows network machines will not "SEE" you.

2) ping.....good
3) net view \\computer name...good, if not then make sure you are running a WORKSTATION service (aka client for microsoft windows). reboot
4) get a browselist....good, if not then make sure some computer on the LAN is running a SERVER service (aka share a drive/printer). WATCH THE POWER SAVINGS CRAP, TURN IT OFF.
5) switch to another operating system

Your ever cynical,
spidey

 

[spidey07]

TERREAPART:

good note, nice catch.

 

[themadmonk]

Fixed the problem. Reverted back the Original Installation of Windows 2000 and now it works. I believe it was a Services problem. I tried some tips from a Website which told me which services were not needed in order to save on memory. However I disabled something that should not have been disabled.
Thanks again for all the help.

 

[BreakApart]

My bet is you disabled the computer Browser service...

I have seen people shut this one down for the SAME reasons you did--they wanted the MAX performance.

I must say w2k does have HUNDREDS of tweaking options. It can easily get confusing knowing what is needed and what is not...

Good Luck...

 

[Bleep]

Hey guys
Some really good troubleshooting tips here, a copy of this thread will go in my troubleshooting archives.
Bleep