1 Server, 2 NICS to 2 VLANS 2

[dibthree]

Server Nic 1: Connected to VLAN 1
IP - 192.168.1.10
Subnet - 255.255.255.0
Gateway - 192.168.1.1

Server NIC 2: Connected to VLAN 2
IP - 192.168.2.10
Sunbet - 255.255.255.0
Gateway : none

Server communicates with devices on VLAN 1 through NIC 1 with no problems.

Server does not see anything on VLAN 2 even though it's second NIC is on VLAN 2

How can I make this server see both networks?

Thanks for you help.

 

[unclerico]

what kind of switch are you using and does it support the use of VLAN's?

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[dibthree]

cisco. yep.

 

[theravager]

Use the route add command to put a static route for the 2nd network

 

[ADB100]

Multihoming Windows.....

I have never had any good experience with Multihoming Windows servers. I am sure you can get it working but Windows is much easier if it only has a single IP address.
What's the reason for the multihoming? If its just to increase bandwidth why not team the NICs? and route the 2nd subnet?

Andy

 

[dibthree]

It is a management Server that manages SAN hardware on one subnet and and ESX & VM's on the other network.

In response to the earlier post about adding a route - It is a Cisco Gigabit Managed layer 2 switch so I do not think I can add routes in the switch.

 

[unclerico]

show your switch config. in theory how you have the NICs configured on the server side should work so I'm wondering how your switchport(s) is(are) configured.

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[hughejars]

Surely VLAN2 also requires a gateway address, otherwise nics/clients on that side of the network can't get out to other parts of the network.
As you say 'VLAN1 has a gateway address and sees the other network ok.'

Working towards my MCSE/A and CompTIA. Any help greatly appreciated.

 

[theravager]

The route has to be added on windows the command will be something like
route add 192.168.2.0 mask 255.255.255.0 gateway 192.168.2.10

Once you have it working use -p to make it permanent thru a reboot.

I'm a bit rusty but something like the above will be close.

The vlan side of things is irrelevant as to the network card its just a normal subnet. Some cards are vlan aware but in this case theres no need for those features.

 

[unclerico]

Surely VLAN2 also requires a gateway address

No actually it doesn't. The gateway address is simply there for times when the host doesn't have a route to get to a destination. The reason you only want one default gateway defined when your host is multihomed is because you will get two default routes (obviously). The problem comes in when the host needs to cummunicate with a host outside of its known subnets. The local routing table will look like this:

Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0    192.168.1.1    192.168.1.10       [b]25[/b]
          0.0.0.0          0.0.0.0  192.168.2.1   192.168.2.10       [b]20[/b]

The key above is the portion in bold. Unless you set the default gateway on the second and subsequent NIC's to a higher metric, all traffic destined for the default route will go out the incorrect interface and basically disable the ability to communicate outside the known subnets. Since the host has addresses (routes) on two subnets it will be able to communicate just fine. ADB100 would be able to speak more to this since dude is a routing guru.

the OP needs to make sure the switchport his second NIC is connected to is set to access VLAN2 and not set to access VLAN1.

Also, it would probably be best to uncheck "Register connection in DNS" within the second NIC's properties.

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[hughejars]

Still so much to learn!
How did you get on dbullion?

Working towards my MCSE/A and CompTIA. Any help greatly appreciated.

 

[dibthree]

Sorry I have not checked this in a few days. I am on vacation in the Florida Keys so I am checking work stuff only once in a while.

Thanks for everyones input. I am going to try adding the route via windows, and I will let everyone know how it works.

If that does not work when I get back to the office I may just add a router on a stick with an old Cisco 1700 I have in a box somewhere.

Thanks again, and I will keep you up to date.

 

[dibthree]

Ok here is my routing from Windows. I can not ping anything on the 10.10.11.0 network. It looks to me like it should work because I see the route for the 10.10.11.0 network via the gateway 10.10.11.222 NIC.

Any help is greatly appreciated. Does anyone see what I am missing? Might it have to do with the metric?

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.10.10.250 10.10.10.225 10
10.10.10.0 255.255.255.0 10.10.10.225 10.10.10.225 10
10.10.10.225 255.255.255.255 127.0.0.1 127.0.0.1 10
10.10.11.0 255.255.255.0 10.10.11.222 10.10.11.222 10
10.10.11.222 255.255.255.255 127.0.0.1 127.0.0.1 10
10.255.255.255 255.255.255.255 10.10.10.225 10.10.10.225 10
10.255.255.255 255.255.255.255 10.10.11.222 10.10.11.222 10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 240.0.0.0 10.10.10.225 10.10.10.225 10
224.0.0.0 240.0.0.0 10.10.11.222 10.10.11.222 10
255.255.255.255 255.255.255.255 10.10.10.225 10.10.10.225 1
255.255.255.255 255.255.255.255 10.10.11.222 10.10.11.222 1
Default Gateway: 10.10.10.250
===========================================================================
Persistent Routes:
None

 

[dibthree]

OK I feel dumb. But I could not leave you guys hanging.

I found the problem. I had the second NIC on my server patched into the wrong port on my Cisco Switch.

Thanks everyone for wasting your time with me.

It is one of those dumb mistakes that caused me literally days of troubleshooting. If I had not been out of town working remotely I hope I would have caught it earlier.

I just assumed I had patched everything in the same way I had written in down on paper in my design.

Thanks again.