• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Win 95 and W2K Server

H

Hoober

Diamond Member
I'm setting up an SMS lab as a demonstration for the higher-ups, so I need to offer them a taste of everything that we have in the inventory -- including Win95 beaters. I've got everything setup through a hub. For now I've set everything to look at a workgroup (I haven't set up the domain yet, I wanted to make sure I'd get connectivity from all the machines first) but right now the only thing that will see all the machines in network neighborhood is the Windows 98 machine. The two W2K machines (Professional and Server) won't see the 95 box, and the 95 box will only see itself and the 98 box. Both 95 and 98 have print and file sharing on... any suggestions?

 
To see the win2k machines, you have to add the users to the win2k machine and then give them permission to access each resource.
 
And that's only in regards to the 95 OS? Because the W2K machines can see 98 just fine...

Also -- on the W2K server you don't add users... I mean, in the typical W2K professional sense you don't add them.

Didn't work...

Another interesting piece: just got finished building one with WindowsME -- it can't find the 95 machine, either.
 
OS shouldn't matter, what protocols are you using? TCP/IP or Netbeiu? You have all the machines in the same workgroup so that's not an issue. Can you ping the win2k machines with the 95 machine?

Try reinstalling the tcp/ip protocols, almost sounds like they didn't take...
 
Yeah, I thought about that when I was walking back to my office from the lab. I'm going to try reinstalling Netbeui on the 95 machine...

The other interesting setup thing is that none of the computers, besides the server, have an IP address as of right now. So long as their not accessing outside resources (other than the mini-LAN they're on) they shouldn't need them, right? Of course, once I set up the domain they'll get IP's from DHCP, but I didn't think workgroups needed them????
 
If you can help it, don't use Netbeui, use tcp/ip. You may be having a duplication problem with the Netbeui protocol. Set each comp up to use dhcp and let win2k server assign them an ip addy.

You don't have to totally configure the win2k server with a domain, just assign it a static addy of 192.168.0.1, subnet of 255.255.255.0 and let the other machines request and receive an ip from the server. OR, you could just assign static ip's and not worry about dhcp. Either way I'd delete the netbeui protocol and go to tcp/ip.
 
Just reinstalled TCP/IP and it still won't communicate with the newer OS's. Its not a big problem because I know I can force it to see the server and the other machines once I get the domain up, I was just curious as to why 95 would do that.

Thanks for your help, Rusty. I appreciate it.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top