I am trying to set up a small LAN with 2 PCs, one running Win98 and one with Win95. I had the network going with NetBEUI, but I would like to use TCP/IP. I removed NetBEUI and IPX from both machines leaving just TCP/IP. Both are configured for the same workgroup and have unique names and IP addresses. The machines are connected to a 10BaseT hub, and both have something shared (with share-level access). I set the primary logon to Client for MS Networks on both PCs. Now here's where it gets weird. I can logon to the Win95 machine with no problem. When I try to logon to the Win98 machine, it asks for a user name, password, AND a DOMAIN (the Logon to Windows NT domain is NOT checked in the Network properties). I tried my normal user name and password and several things for the domain, including the name of the PC, but I can not logon to the network. I get a message saying that my "name and password can not be validated on the network" (or something similar). At this point, my only choice is to boot in Safe Mode and change the primary network logon back to Windows logon so I can get into the system again. Anyone know what could be causing this? Why is it asking to logon to a domain to authenticate my password? Any help or suggestions would be appreciated. Thanks, NuGGetBoY

If you just have 2 computers, just hook them up with a crossover cable. Much less margin for error. The hub is not needed. Hubs are not necessary unless you are using 3 or more computers.

I am not only doing this for file sharing, but also to learn networking with TCP/IP in order to get certified, and there will be more computers added later. Eventually, I will have NT server running, so that will eliminate this problem. However, that may be a while. There must be a solution or workaround to have Win95-Win98 TCP/IP network going. I have seen it done before but I no longer have access to the setup. Anyone else have a suggestion? NuG

Lets start from the ground-up. Make sure Client for MS Networks exist on both computers if not add them. Add TCP/IP which is the protocol used by the NIC on both computers. Setup the address and values needed. Pick a primary logon. Both of them works fine. The difference is the login-in screen. If all users uses the same desktop configuration, pick windows logon if not pick the other one. On that point, make sure to mark "quick login" on Client for MS Networks. I recommend that you use NetBEUI instead of TCP/IP. Look-up this webpage www.grc.com for information.

Using TCP/IP works. Just use 'windows logon', assign computer names to both (such as PC95, PC98), IP address (90.0.0.1, 90.0.0.2), mask the same for both (255.255.255.0), workgroup HOMENET on both PCs, set 'File/Printer Sharing' on both PC, restart PCs, then set some folders for sharing by right click on the folder while in explorer, select share, set sharing level, name etc.. then in the network neighbourhood, you should see each others.

Basically your Client is looking for username and password verification from a domain controller which you find on Windows NT servers (Gawd bless'em) . As you do not have either a primary or secondary domain controller running on your 2 user network Windows cannot verify your details and will prevent you from completing login. The question is why ? if you say that Domain section of your MS CLient is not checked. Did the offending machine come from a LAN originally ? If you are happy that ip is installed correctly on both machine then I would suggest the removal and reinstall of MS client on workstation that is playing silly buggers to see if you can overwrite the stray domain specific value. Dont worry about your choice of protocol. Its practically standard on most Networked machines thesedays and should be the one to concentrate your study on. LONG LIVE IPX/SPX

Thanks Damien. I realize what it was asking for in the logon since I have worked with NT server before, but I also thought it was odd that it wanted to logon to an NT domain since that option was not selected. And this machine was not previously part of any network. I just recently added the NIC. I guess I'll try reinstalling the client or try using Windows Logon on both PCs...