2 Nics, 2 Networks

Salt February 8, 2009 at 08:58:05
Specs: Windows Vista Ultimate

Currently in a situation where there are a number of users all connected to a switch (which I don't have access to) which is then connected to the internet. This switch turns 'off' automatically at 11.00pm, and 'on' at 6.00am and uses MAC address filtering to regulate who/what is on the network. I also have a wireless router (which I do have access to) which is connected to a 1TB NAS box. The users on the wired network currently connect via wireless to the NAS box for basic file sharing. My computer is connected to both the NAS box and the wired network by wire (I have 2 NICs). My question is this: is it possible to route the NAS shares through the wired network to the users by using my computer as a sort of router between the 2 networks?

Below is the information about subnets and IPs etc which I have pulled from running the command "ipconfig /all":

Wired Network (that I cannont access):
DHCP Enabled: Yes
IPv4 Address:
Subnet Mask:
Default Gateway:
DHCP Server:
DNS/WINS Server:

Wired Network (which has NAS and that I can access):
DHCP Enabled: No (although it is enabled in the router configuration ??)
IPv4 Address:
Subnet Mask:
Default Gateway:
DNS/WINS Server:

The router that I have access to is set to assign IPs in the range of upwards. I am surprised that "ipconfig /all" shows DHCP to be disabled for this connection.

Currently, my computer works fine and can access both networks simultaneously. So can I connect both networks? The purpose of connection is not to share the internet connection, but to allow access to the NAS (through my computer) through the wired network for a quicker connection.

Any comments appreciated,


See More: 2 Nics, 2 Networks

Report •

February 8, 2009 at 11:30:45
Just because its enabled on the router doesn't mean its enabled on the client.

That nic is set to a static ip address with no gateway or dns server listed. You should be able to see this by going to the tcp/ip properties.

Google Internet Connection Sharing xp and follow one of the how tos

Report •

February 10, 2009 at 00:47:49
Thanks for the reply.

Using your advice, on the computer connected to the two networks, I have set up Internet Connection Sharing - sharing the wired network that the NAS is attached to it. I have also enabled IP routing. Then, on a computer connected to the switch that I can't access, I have set up the following route:

Network Destination: (the IP of the NAS)
Gatewaty: (my computer)
Metric: 1

Being a bit of an amateur with routes, I was surprised when the above worked and I could successfully connect to the NAS.

However, when someone is 'connected' to the NAS through my computer, and then I try to access it simultaneously using a mapped network drive, the following error occurs:

"Microsoft Windows Network: Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.
The connection has not been restored."

But when accessing it using its IP address in a run command with \\\share - it works fine. Weird.

Anyway, more importantly is the route correctly configured? The IP routing table of the router connected to the NAS can be altered. Do I need to insert a route similar to the following:

Network Destination: (Computers on the network whose switch I can't access)
Netmask: (is this correct? - never understand network masks)
Gatewaty: (my computer)
Metric: 1

(which is essentially opposite to the one above)?

By placing the 0 at the end of the netmask and network destination, does that number become similar to using a *. ie, whatever the number there, does the router still used the above rule? And considering everything 'seems' to be working, is the above route required at all?


Report •

Related Solutions

Ask Question