Discussion Locked

TCP/IP Problems on Win95 Machines

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
On a network with 2 machines on a network using a SMC Barricade 4-port 10/100 Broadband Router the LAN machines can see each other and the internet fine when booted in Windows 2000. When booted in Windows 95 using DHCP it fails to get an address and the IP remains 0.0.0.0. When using static addresses it can ping itself and the router, but nothing else. Ideally I would like the Win95 systems to be able to see each other (or the other one booted in 2000) and be able to use the internet. Otherprotocols seem to give the same result, the system can see itself but not the larger network. The LAN had originally been working, but over the past 6 months it has gone through a large # of changes (IPC, WinProxy, an extra network card on one system, and now the router). I use W2K primarily, but some programs work best in 95. Hopefully a fresh perspective will help.

6 replies

by dheupel

This is probably a name resolution problem. Put a hosts file in the Windows folder on the W95 PC that points IP addresses to machine names. You can find a sample file called hosts.sam in the Windows folder. This will probably solve your problem.Include an entry for your router as well.

by dragon emperor

After many more hours of trouble shooting (which included creating both hosts and lmhosts files) so I had more information and repeated calls to SMC technical support until I actually got someone who felt like doing their job I was told that it was probably a problem with the router and to bring it back to the store for a replacement.

by timber

One other thought would be making sure the workgroup name is setup properly. The names need to be the same on both machines.

by dragon emperor

Since I already had the systems on a LAN before they were already in the same workgroup. The router problems caused the use of TCP/IP to mess up what it was allowing the rest of my network to see.

by dragon emperor

After many more hours of trouble shooting (which included creating both hosts and lmhosts files) so I had more information and repeated calls to SMC technical support until I actually got someone who felt like doing their job I was told that it was probably a problem with the router and to bring it back to the store for a replacement.

This discussion is closed to new replies.