95/2k networking

[Asterix404]

Hello. I have a problem networking 95 and 2000. I know it sounds foolish I mean Why in hell would anyone actuilly have 2000 and 95 in the same house. The answer is simple my dad is the cheepest man to walk the face of the earth. 95 is installed on a 6 year old 133 with 5.1 gig mem so no installing 2k on that. The problem is that 2k recignizes that 95 exists but 95 cannot get on the network, I mean that I get an Error that says that I can't get on the network. Pinging 95 from 2000 is possible and I get the IP that I put on the Linksys router which is 192.168.1.110. When 95 pings itself I type in ping comp name and it gives me 24.180.98.23 which is an ip that I do not recognize. My home ip is 24.180.98.110 wich is the router ip. If I ping 95 using 192.168.1.110 it goes through. Can anyone tell me why I have 2 ip's on one computer?

[scrotus]

THis is what I have found with networking Win2K and any other OS. I run Win2k and 2 win98 machines behind the linky 41. I had trouble getting the 98 machines to acces anything other than the win2k's IPC$ folder. Finally did this and its the easiest way.

Create a user on the Win2K machine with the exact logon and password as the 95 machine. Example, on Win2k, create user Dad with password dad. Give that users whatever right you want to assign. Make sure you are sharing the drives you want him to see. (not the secret pr0n collection :) )

Then, do find computers from the win95 machine, search for the win2k computer name and it should work. Then you can map the drive.

Are you using netbeui as the LAN protocol? That is the best for using within the LAN.

Also, is you go to the Microsoft knowledge base and search for networking windows 2000 windows 95, there is a great FAQ on how to do it. Thats where i found the info.

[cyberskye]

What he said^

then, if you still cannot connect:

run "winipconfig" at the command prompt on the 95 box and run "ipconfig" on the w2k box. Make sure that both have private (192.168.x.x) addresses and the same netmask. The router should be the only machine with a public (24.x.x.x) ip address. I might uninstall and reinstall tcp/ip if things are acting funny. MS does not have the most robust stack around.

That was weird about the ips...


Good luck,

Skye

[YeOldeStonecat]

Yes you need to create accounts on the NT boxes to let other machines access shares. NT is an operating system designed for corporate networks, and it has security to go with it. It's not as easy as the home consumer operating systems of the 9X family.