"Not accessible" & "Network path not found" messages

[videobruce]

Two boxes, both w/ XP Pro, both have same username and workgroup ID (not that it matters), both are setup up for simple file sharing on all drives and both go to a router.

Both have internet access, box one can 'see' both computers, box two can't 'see' either computer and neither can see one another.

I can 'ping' the router on both, I can ping eaches own address, but can't neither can ping one another.

How can you not see your own address under 'View workgroup computers'?

What's wrong?

[glc]

1. http://forum.pcmech.com/showthread.php?t=165490
2. Make sure file and print sharing is enabled in the Windows firewall exception list on both computers - and uninstall any 3rd party firewall. If you are using a 3rd party firewall, you must disable the Windows firewall and configure the 3rd party properly.

Most commercial 3rd party firewalls can be configured properly, but freebies can be more difficult, if even possible. For example, Zone Alarm Free requires you put the whole router subnet in the trusted zone *and* the Internet firewall dropped down to Medium protection. What I do to get around this is install NetBEUI for file sharing, then I can leave ZA at defaults.

[videobruce]

I'm using Kaspersky Antivirus V6, I'm NOT using Windows Firewall (it's disabled).
I'll look that over.

[glc]

If you don't want to keep screwing around, install NetBEUI. If it doesn't work you have a core OS issue with one or both of the computers.

http://support.microsoft.com/kb/301041

[videobruce]

That link refers to Home & Pro. I only have Pro running.
Both boxes have passwords.
File & Printer Sharing is enabled.

Why NetBEUI??

[glc]

The second link explains how to install NetBEUI on *any* version of XP. The first link was for you to review and see if anything in it applied.

Why? NetBEUI is an old protocol, it predates TCP/IP in Microsoft networkable operating systems. It has NetBIOS incorporated, it requires NO configuration, it is NOT Internet-capable, it's secure, it just WORKS. It was made for simple LAN file and print sharing. It's one of those old school things that is being abandoned, but it still has its uses. The only downside to its use is it's quite "chatty" and will degrade LAN performance when you get more than 4 or 5 systems up and talking to each other. I use it on my LAN because I don't feel like messing with TCP/IP issues with firewalls, etc. Whenever you use TCP/IP for filesharing on a LAN, you have potential exposure to the outside world that needs to be properly secured. My machines have both TCP/IP and NetBEUI installed, the TCP/IP works for the Internet and NetBEUI works for LAN filesharing - I have NetBIOS over TCP/IP disabled - bingo, my LAN shares are effectively invisible to the Internet.

Here's a long read for you:

http://www.grc.com/su-explain.htm

It was written before Win2K/XP, but its basic principles still apply. In XP, you can accomplish essentially the same thing by simply disabling NetBIOS over TCP/IP. This is done in TCP/IP properties, advanced, WINS tab.

In a nutshell, I'm not necessarily telling you to install NetBEUI, but it's a easy thing to do to try to get filesharing working when it's not cooperating, and it has its security advantages.

[videobruce]

NetBEUI is an old protocol

That's why I asked.

I also tried my Laptop that has a unmodified version of XP installed and there are no issues there. Box 1 that work either way thoiugh I find Box 1 to be slow in reconizing the Laptop where the Laptop 'sees' the network much faster. Box 1 & 2 have a nLite complied version of XP Pro, the Laptop just has a XP Pro w/sp2 slipstreamed.

Before you ask, I did look over the services and don't see any issues. Other than the 'slower' response of Box 1 compared to what it should be, both used the same CD.

Customized by nLite v1.4.1 - www.nliteos.com Components removed: Accessibility Options Briefcase Games Internet Games Pinball Screensavers Display Adapters (old) IBM PS/2 TrackPoint IBM Thinkpad Logitech WingMan Microsoft SideWinder Serial Pen Tablet Sony Jog Dial Tape drives Toshiba DVD decoder card Brother Devices Gravis Digital GamePort Iomega Zip drive Images and Backgrounds Luna desktop theme Music Samples Old CDPlayer and Sound Recorder Client for Netware Networks MSN Explorer Netmeeting Windows Messenger Search Assistant Tour Messenger DOCS SUPPORT VALUEADD Languages

Other than the Client for Netware Networks, MSN Explorer & Netmeeting, I see nothing that would have anything remotely to do with networking. I'll just re-install looking for the problem before I install all the other 'stuff'. Actually, both boxes are the same except for the video card, the drives & memory and those are only different manufactures. I was going to make a 'master image' for both machines with just what I call 'base' programs installed and the drivers minus the video for a backup but never did.

[videobruce]

How about the SAME identical MAC address on BOTH MBs' ethernet controller???
I switched to the 2nd controller on one box (w/ a different address from the first controller) and all is AOK.

I thought every ethernet device (even the same model) had a different address?

[glc]

I'll have to remember that!

[videobruce]

The temporary solution is to use the 2nd adapter on the 2nd MB w/ the different address.

The manufacture suppects a corrupted bios and suggested re-flashing both MBs', but directly in DOS, not through Windows which I did the first time using their "LiveUpdate". Anyway, how could the addresses from one MB transfer to another? The only common link is the router.
There are stickers on the MB w/ each address, but not in hexdecimal and all four addresses are different.