troubleshooting MS networking - can't see my computer??

[spidey07]

check out these links, hopefully it will help with "can't see my computer"

WinME problems

nt and 2000 troubleshooting

more of the "microsoft knows this is a bug...sorry, can't help ya. Buy more of our fabulous products"

pay attention to the "registration and propogation time"

hope this helps. A few ways to avoid all this trouble
1) run WINS - although not acceptable in home environment
2) run NetBeui
3) Use a LMHOSTS file - probably the most sound solution

cya!
spidey <---bored 'cause i'm sick

:frown:

 

[TimeThrash]

Same workgroups? Are you doing a crossover connection here or what? I noticed the NetBeui. More info.
Tt

 

[Shadow07]

Dude, what is going on? Fealing under the weather?

BTW, I would NEVER install NetBEUI to get it to work with other Windows clients. Most problems have to deal with the NetBIOS Master Browser not being set on a computer. If you have Windows 2000 or NT workstations, you will have no problems. If you have all Windows 9x machines, then you need to set one machine to be the Master Browser. To do this, goto the Properties of Network Neighborhood and then make sure the Printing and Share services for Microsoft Networks has been installed. If so go to the properties of this service. Make sure that the Master Browser is set from Automatic to Enabled. This only needs to be set on one machine. That's it.

He's not posting he has an issue, but rather sites that can offer suggestions or leads to the problem.

Feel better Spidey. <-- For once, Shadow is giving Spidey some nice and helpful words, instead of giving him crap.

Oh, wait. I think one of your routers just went down! HAHAHAHAHA. <-- Looks like Shadow is giving Spidey more crap.

 

[Shadow07]

Damn DP!

 

[spidey07]

router go down, gimme a break. haven't seen that happen in years. thanks for the thoughts though...my head/sinus is killin me.

SHADOW07, i'm posting this because there seems to be a lot of difficulty with peer-2-peer networks of 95, 98, 2000, ME or any combination therof. My stock answer has been to install netbeui only because it gets rid of the added complexity and browsing issues of IP. Then, quit rebooting the machines and let one settle down as the master browser.

That's where the power only one machine up and wait 10 minutes before powering the other one.

You being the MS guru, maybe you can shedd some light on this. These kinds of &quot;i can't see my computer&quot; problems seem only to happen to people who are doing peer-2-peer. if there is some kind of server the of course that will always win MB elections. search on some of my previous posts.

timethresh - no trouble. Wanting to post some good resources for the poor souls out there having so many problems with MS networking, err. I mean MS notworking. To people like shadow troubleshooting masterbrowser issues is second nature, more of an art than a science.

 

[Shadow07]

I was just messing around. I know that you're at home sick, I just wanted to play around. Anyways, I am always glad to see you post links and tid-bits for people on easy issues. But, just do what I said in my first post, and that should resolve the browsing issues.

EDIT: TCP/IP is not the &quot;browsing&quot; protocol. It's NetBIOS over TCP/IP. Actually, UDP is the transport protocol, but the session protocol is NetBIOS. Most packets and sessions are SMB (CIFS; that's Common Internet FileSystem; for Windows 2000/XP machines).

 

[spidey07]

that is my whole beef with browsing via a UDP broadcast. just doesn't make any sense. Not to mention all the overhead with tcp/netbios/smb, heck there's hardly any room for data!

 

[AKA]

Some of the &quot;I cant see my computer&quot; problems of late, seem to be happening with Win2K. Which I think ive seen both of you post in. So it can happen when Win2K is involved. Although I know of one which nothing done would resolve it, I think he formatted and reinstalled.. worked fine after that. Some examples:

Link

Link

Link