Dual homed Windows 2000 server not accessible from win 95 clients


I recently enabled the second network interface on one of our Windows 2000 servers (standalone print server) to connect to a second network (for remote WAN access). In doing so, our windows 95 clients could no longer see the server on the first interface. When I disabled the second interface, they can see it, and access the printers again. Win XP clients can access it ok without the problem.

We already have 3 other servers configured in this way, which are not accessed by the win95 clients,  but I noticed that these are not accessible either, but servers with only one interface in use are accessible.

Who is Participating?
nazirahmedConnect With a Mentor Commented:
right, try adding another gateway on win95 pc as, if doesnt wory, remove the gateway from the win95 and see how it goes.
have you tried ping the  interfaces , and or the server from the win95 machines.
IvorStonesAuthor Commented:
Yes, the Win95 PC's can ping all the dual homed servers when both intefaces are enabled, but they cannot "find" the servers or access file & print unless the second interface is disabled?

They do not use the second network at all and have no need to.
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

Hi IvorStones
what is the default gateway set on the win95 machines? are win95 getting any wins or dns settings? if so, from where and what are the wins and dns settings.
IvorStonesAuthor Commented:
They have manually entered IPs for PC, gateway and DNS, all are on the LAN network same as the server's  first network card and are working happily.

Only when I enable the second network card on the print server (with a different network address) do they stop working.

Server is with gateway, DNS
PC is with gateway, DNS

When the second network on the server is disabled, the above works fine.

When I enable the second network card on the server as, gw192.168.0.135, dns192.168.0.209, then the win95 PCs can no longer access or "see" the server on
They can ping, but cannot browse or "Find computer". Typing \\servername or \\ in the run box doesn't work either. This only affects Win95 PCs, not XP, which still "see" the server(s).

IvorStonesAuthor Commented:
On the win95 PC's I added an IP to the gateway list which is the address of another dual homed server that is not used by the win95 PC (see 1st post) and it was then accessible. I then enabled the second network on the new server, added it's address as another gateway on the win95 PC and it could be "seen", but then the first one could not. After some experimentation, it would appear that adding the server as a gateway fixes the problem, but only for one server since win95 only seems to use the 1st two entries in the list of gateways.

This solves my immediate problem.

My best future route will be to replace the win95 PC's with WinXP PC's (shame, they are only used for good-in and despatch).
well..they should be able to see the gateways mentioned in the list, atleast i had similiar issue where i had 3 gateways and all of them were working. i think maybe changing the order of gateways(on win95 pc) solve your problem comletely.
IvorStonesAuthor Commented:
I tried that, only one additional one seems to work.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.