Interesting networking problem

[Prisoner_Number_Six]

Networking between two computers either using a crossover cable or a switchbox is extremely straightforward, as long as the setup is correct-- workgroup names, file and print sharing, and so on. Plug it in and set it up, and it works or it's usually a hardware problem (Linksys routers have a high out-of-the-box failure rate, for example).

My "unsolvable" scenario is this: I have an XP machine and a Win98 machine, both of which network perfectly with other computers (I tested them both with a laptop and a crossover cable, and separately with a switch box and normal patch cables I tested on different machines before hooking it up to these machines). However, they WILL NOT TALK TO EACH OTHER.

I've checked everything up to and including firewalls, etc. They simply do not see each other, although both separately will instantly hook up to other networks, including my home system (said network using an AirLink router, a couple switch boxes and a wireless access point to hook up to Comcast. It consists of both XP and Win2K machines).

I'm stumped. Oh, btw, the Win98se machine is a fresh install on a scrubbed hard drive. All drivers are present and all cards have been tested.

Any clues for someone who is obviously missing something obvious (that is probably doing everything short of reaching out and slapping my face)? I know when I figure it out it'll be a real Duh moment, but I never said I knew everything about everything.

[WLKjr]

1. TCP/IP added to both machines?

and by talking are you meaning getting the 98se box to talk to xp and 2k or vice versa? On xp and 2k you can see all ntfs and fat filesystems, so if you have a shared folder on the 98 box from 2k or xp you can see it. On the other hand, 98se only supports fat filesystems and cannot see ntfs partions. Also, check your share permissions.

[Prisoner_Number_Six]

2. The file systems are translated- NTFS or FAT32 don't matter

when mapped to over a network. It's the same principle that allows a Windows machine to FTP into a Unix server. Win98's only networking restriction is it can't see workgroup names if they're over 12 characters long.

I hook all my client's Win98 machines into my local network when in my workroom, and they see my NTFS file directories perfectly. It's how I install my standard software packages-- networking to a mapped drive is a LOT faster than installing from cds.

[WLKjr]

6. wow what a brain fart I had, sorry

I just reread my post.

[Squeegee]

3. Are you using XP Home Edition?

I found that Home edition does not automatically find network file systems on my home network, though XP Professional does.

[Prisoner_Number_Six]

4. Nope- Professional Edition

And it's a mutual invisibility-- neither machine sees the other, even though networking is installed and configured on each machine and all hardware has been independently tested.

[Hokie]

5. Can you ping the other machine?

That is where I usually start with network problems. I have heard of this problem before between Win XP and Win 98 machines.