[Webinar] Streamline your web hosting managementRegister Today

x
?
Solved

Routing Problems on VM

Posted on 2013-11-18
3
Medium Priority
?
217 Views
Last Modified: 2014-01-21
Hi

I have a Virtual machine configured with windows 2008 R2 and Two NICs in a VMware Environment. The virtual machine has one nic in the Production Network and the other in the DMZ. it is suppose to send traffic destined for 10.*.*.* network to the nic with the gateway of 192.*.*.* how ever after a day or two communication stops. if you reboot the APN in the DMZ and reboot the server communication continues. Any idea?
0
Comment
Question by:Helao Mwapangasha
  • 2
3 Comments
 
LVL 13

Expert Comment

by:SagiEDoc
ID: 39658681
You can add a static route on the server. Open a command window and type:

route add 10.*.*.* MASK 255.0.0.0 192.*.*.*

Clearly do not use "*" if the destination network is 10.51.1.0 use that and the final IP is the actual gateway. Ensure that you only have one gateway entered on one network card. So typically you would have your production network listed. The NIC for the DMZ should have no gateway listed.
0
 
LVL 3

Author Comment

by:Helao Mwapangasha
ID: 39658992
Hi SagiEDoc

I do have routes config. Internal LAN has no Gateway specified and the DMZ Lan has one

Sample route print is attached
routes.PNG
0
 
LVL 13

Accepted Solution

by:
SagiEDoc earned 1000 total points
ID: 39659023
I had a similar issue where VM's would loose network. I am not sure if you have a similar setup but this is what I traced the problem to.
I had two network cards (physical) connected to the virtual network. One of these cards was working fine, the other had a misconfigured VLAN. If the virtual network connected to the problem NIC the VM lost connectivity. Once I corrected the problem it all came right. I picked up the problem by looking at the observed ranges of the virtual network (screen shot attached)
I corrected the problem but also to manage this problem in the future I set the Network failover detection to Beacon probing (another screen shot attached.) The default setting is link status which basically means if there is a network cable plugged in and the link status is good then all is well.
By changing this setting it allows VMware to failover the NIC's if there is an issue on the network even if the link status is good. I hope this solves your problem.
1.JPG
2.JPG
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is in response to a question (http://www.experts-exchange.com/Networking/Network_Management/Network_Analysis/Q_28230497.html) here at Experts Exchange. The Original Poster (OP) requires a utility that will accept a list of IP addresses …
Resolve DNS query failed errors for Exchange
This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

590 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question