Accessing shares on dual-NIC server: should be so simple?

  • Thread starter Thread starter Jezza
  • Start date Start date
J

Jezza

I have a Windows 2000 server called SERVER, dual-homed 192.168.1.10
and 192.168.2.10, serving two subnets 192.168.1.0 and 192.168.2.0

In our DNS, SERVER has the address 192.168.1.10

I simply want users on the 192.168.2.0 subnet to access the server via
the server's second NIC 192.168.2.10 rather than going via the router.

I am trying to map a network drive for these users via NET USE H: \
\192.168.2.10\sharedfiles but get "system error 64 has occurred. The
specific network name is no longer available"

When I try NET VIEW \\192.168.2.10 I get "system error 53 has
occurred. The network path was not found"

If I do NET USE H: \\SERVER\sharedfiles or NET USE H: \
\192.168.1.10\sharedfiles then it's fine, but both then go via the
router which is what I want to avoid, hence the fitting of the second
card.

Any ideas?
 
Jezza said:
I have a Windows 2000 server called SERVER, dual-homed 192.168.1.10
and 192.168.2.10, serving two subnets 192.168.1.0 and 192.168.2.0

In our DNS, SERVER has the address 192.168.1.10
Click to expand...

Then that is the one they will use,...it doesn't matter if you put 15 nics in
the machine.
I simply want users on the 192.168.2.0 subnet to access the server via
the server's second NIC 192.168.2.10 rather than going via the router.

I am trying to map a network drive for these users via NET USE H: \
\192.168.2.10\sharedfiles but get "system error 64 has occurred. The
specific network name is no longer available"
Click to expand...

That is because an IP# is not a "network name".
When I try NET VIEW \\192.168.2.10 I get "system error 53 has
occurred. The network path was not found"
Click to expand...

Net View is Netwbios based and expects a Name.
Any ideas?
Click to expand...

Your first option would need a second DNS Server in the 192.168.2.x network that
has the names/IP#s statically entered into it for the machines you have involved
as "targets". This DNS would use the other DNS as a "forwarder" in the
Forwarders List. The Client in that segment would use this DNS instead of what
they have been using.

Your second option is to use a HOST file with a "fake" name for that server. Use
the HOST file on all the related Clients in the 192.168.2.x segment. Use that
"fake" name anytime the server is referenced.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft, or
anyone else associated with me, including my cats.
-----------------------------------------------------
 
That is because an IP# is not a "network name".
Click to expand...

It's not a network name, but it works. I do it all the time. In fact I
just did it.

--------------------------------------
C:\>net use M: \\192.168.0.5\jeffmusic
The command completed successfully.
--------------------------------------

Make sure client for MS networks and File and Print Sharing are
installed and enabled on that NIC. Make sure you're using \\ and not //!

....kurt
 
Ok.
I started second guess myself after I sent that, too.
Anyway, I think he has to come up with a proper Name/IP relationship to get the
multi-nic thing working right. There are too many strange ways people can hook
things up together in LAN topology so I doubt I can suggest anything more than
that.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft, or
anyone else associated with me, including my cats.
 
Back
Top