98-to-2k Cross-over Filesharing

[ChromWolf]

Buddy of mine has a 98 laptop (I forgot to check if it was 98SE or just 98) and a 2k desktop, which he's networking together using a crossover cable. There's no router in the picture, and even so, he's still on dial-up anyway... bleh.

In any case, he's having trouble doing filesharing between the two. The 2k box sees both itself and the 98 box (and access files shared on the 98 box), but the 98 box can see neither (not even itself). We had intermittant access to the 2k box from the 98 box, but only after tinkering with settings, and even then, it would ask for a password if he just went to "\\computername", without including a share name (we determined this was because the 98 box was trying to come in on the ipc$ administrative share...? Don't know why it wants to do that...) After being asked for the password, I tried coming in on the c$ admin share, which it simply didn't find (the connection may have failed at this point, I don't know). However, it seems to me that since the 98 system can't even see itself, this is a problem with that system.

both systems, not having a router, are using APIPA for IP addresses, and were both on the same network based on IP address and subnet. The 98 system has NetBEUI installed (in addition to TCP/IP, of course), but I also forgot to check to see if the 2k box had it installed---and I even thought to myself that it needed to be there since a 98 box was on the network! Smacking myself for that one...

I tried a static IP similar to an APIPA-assigned address, and set it just two greater (i.e. if one was 169.254.xx.126, then I made the other 169.254.xx.128). Again, subnet of 255.255.0.0, so same network (and even so, I made the 3rd octect the same for on the 2k box as on the 98 box). This was the tinkering I mentioned that seemed to jumpstart things for a moment, but then we lost it again.

Unfortunately, I don't have regular access to these computers, so I can't just check tomorrow or something and get more details. To restate, I don't know if the 98 box is 98 normal or 98SE, nor do I know what SP that 2k box has. I also missed if the 2k box has NetBEUI installed, I'll definitely check that.

My real questions are, what would make the 98 box not see itself (I did have to switch it to log on using Client for Microsoft Networks, no change), and is there anything other than the 2k box lacking NetBEUI that might prevent file sharing, or cause what's going on here?

[GaryRouth]

One of the wierder things to look at it is the length of the name of the Win2000 computer, or any shared resources on it. I seem to remember that there is a 15 or 16 character limit that Windows 98 has (whether SE or original). I don't have my Win98 notes with me at the moment, but I can check tomorrow. The shared resource naming conventions are much more generous in Win2000.

Enabling NetBEUI seems like a good idea too, though I haven't dealt much at all with crossover cable connections.
. . . Gary

[ChromWolf]

Good call on the character limit! That's actually through NetBIOS, and yes, it's 15 characters (16 with the hidden hex character at the end of the name to indicate service type). Counting it out, both 98 and 2k system should be around 10 or 11, if I recall their names correctly.

I'm assuming the crossover cabling is fine, since the 2k system can access shared resources on the 98 system.

I'm pretty sure I'll need to turn NetBIOS on for the 2k box, but I don't think that would matter for the 98 box not seeing itself, however.... I told the guy I may need to completely un/re TCP/IP, as I know 98 networking (especially 98 normal) was a pain, but I'd rather not do that if I can try other things that might work as well. ....I remember having to rip out a TON of files to do a FULL uninstall of it all---well, maybe just DUN, but still....

[glc]

Here is what I would do - after confirming same workgroup and allowable computer names:

On the 98 box, unbind TCP/IP from the NIC, leaving only NetBEUI bound to it. (The only TCP/IP binding that you need is to the dialup adapter - and this will shorten the bootup time by about 90 seconds) Set it to Client for Microsoft Networks as primary login, and note the username/password used to log in. Ensure file and print sharing is enabled.

On the 2K box, add a local user, corresponding to the login used on the 98 box as previously noted. Add NetBEUI. Create new shares, you can't access the existing $ shares.