Network browsing problem from hell

[Nexworks]

I have two Windows XP Pro machines. PC1 is .2 and PC2 is .3 (router is .1). I can ping both machines fine. I can manually type in \\PC1 or \\PC2 and access each others shared drives fine. I can copy files between the machines fine. However, I cannot browse the network on PC2. Error I get is:

Mynetwork is not accessible. You might not have permission to use the network resource. Contact the administrator of the server to find out if you have access permission.

PC1 can browse the network just fine. Ive had this error for ages now. Its not serious, but it is extremely annoying and I really would like to know what causes it. Reinstalls of windows have come and gone and the problem persists. I have tried different network cards and still same problem. I have even changed the network cables just for kicks and nothings changed. Any ideas?

 

[fractilian]

I'm sure it has to do with permissions. I have a similar prob. I seem to have difficulty translating W2K actions into XP actions.
Well actually its not my computer its on a friends...so there goes the true motivation to solve Sorry

 

[Xtremist]

I'd turn off simple file sharing personally Probably won't fix anything but it can cause some weird stuff to happen I've noticed...

 

[azkiwi]

Start back at square one and work your way through the list. I don't think its permissions - I've had similar errors between XP and 2K and it was configuration. Check your workgroup / computer names etc are all unique and in order, turn off things you aren't using (ICS etc). There are many switches in XP in different places to check.
Can you configure the router OK?

 

[Nexworks]

I am not using simple file sharing. Workgroup and PC names are correct. Router provides internet to all PC's just fine. I can ping all computers and manually type in \\PC2 or \\PC1 and get access that way. So I know the sharing works properly. The PC2 just cant browse the network, and PC1 with the exact same OS and configuration browses just fine.

 

[Nexworks]

Well, I managed to make my problem go away, magically, but just for one session, because when I rebooted PC2 again the problem came back. What I did was removed and reinstalled all network connections on PC1, and as soon as I did that PC2 could browse the network again. When I rebooted PC2, the problem was once again back. Sigh. Why would the networking settings on a pc prevent another pc from BROWSING the network? They can still ping each other and access each other just fine as always. Sigh.

 

[alexXx]

You know what.. in my experience from my network and my school's network, there is most likely no reason at all that it doesnt work. Infact, you may try it tomorrow and it will work, then 2 weeks from now it will stop again. Windows networking is the flakiest POS there is

 

[Concillian]

Originally posted by: alexXx
Windows networking is the flakiest POS there is

I hear that!

 

[Bovinicus]

Just to make sure that it's not a permission problem, assign the Everyone group the necessary permissions on that sure. If it still doesn't work, then you know it's not a permission problem. It certainly seems like one to me.

 

[Nothinman]

Just to make sure that it's not a permission problem, assign the Everyone group the necessary permissions on that sure. If it still doesn't work, then you know it's not a permission problem. It certainly seems like one to me.

On what? On the "My Network Places" icon?

Windows networking sucks, unless you're using WINS or AD/DNS it's going to be flaky as hell and setting up WINS or AD sucks too so pick your poison.

 

[sjgmoney]

I would read Jack's Primers and especially consider using NETBEUI for sharing. I got tired of the TCP/IP nonsense of "now you see the network, now you don't" and haven't had any problems at all since I went with NETBEUI.

 

[fractilian]

I thought Microsoft did away with NETBEUI in XP. I use it for all my W2K machines. Theres too much other stuff tryen to use TCP/IP.

 

[spidey07]

use netbeui, watch any and all browsing problems disappear.

 

[sjgmoney]

Originally posted by: fractilian
I thought Microsoft did away with NETBEUI in XP. I use it for all my W2K machines. Theres too much other stuff tryen to use TCP/IP.

For some reason they did "do away" with it in XP, but the files you need are on the WinXP CD and I recommend setting it up that way. Very easy and as Spidey said "bend over Mary Jane.....errr.... I mean watch your problems disappear."

 

[Savij]

Originally posted by: sjgmoney

Originally posted by: fractilian
I thought Microsoft did away with NETBEUI in XP. I use it for all my W2K machines. Theres too much other stuff tryen to use TCP/IP.

For some reason they did "do away" with it in XP, but the files you need are on the WinXP CD and I recommend setting it up that way. Very easy and as Spidey said "bend over Mary Jane.....errr.... I mean watch your problems disappear."

Not sure I remember this exactly, but the "problem" with Netbeui is that every computer broadcasts itself to the entire network when it connects and broadcasts on a regular interval afterwards. Not a problem on small networks, but when you get into the hundreds of computers it can mean a lot of announcing that computers are still on the network.