Solved

The default gateway is not available.

Posted on 2014-02-09
1
439 Views
Last Modified: 2014-02-10
Hi folks,

Today I encountered one of the most vague problems I have ever seen.

I do have a windows server 2008 r2 as the main machine plus vmware workstation 10 installed on it.

There are three VMs running. One is win2003, win2008 r2, win2012 r2.

They were running smoothly and suddenly their networks stopped except the main server.

When I troubleshooted what it is going on I got the gateway error.

Flushed the dns, renewed the ipconfig, restarted them, reset the networks configs but nothing seems to work at all.

Here is a ping on the main server:

Windows PowerShell

C:\Users\admin>ping 110.245.197.145

Pinging 110.245.197.145 with 32 bytes of data:
Reply from 110.245.197.145: bytes=32 time=6ms TTL=255
Reply from 110.245.197.145: bytes=32 time<1ms TTL=255
Reply from 110.245.197.145: bytes=32 time<1ms TTL=255
Reply from 110.245.197.145: bytes=32 time<1ms TTL=255

Ping statistics for 110.245.197.145:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 6ms, Average = 1ms. 

Open in new window


there is no way out of the blues that such a thing could've happened. I've tried everything and I can't seem to find the issue here.

Any help?

Appreciated in advance.


-----------------------------------------------------------------


This part is added after 15 minutes from the rest above:

:@

I solved it.

For every machine, the network selection specified is Bridged.

When I opened the VMWare virtual network editor I found a couple of created connections such as VMware0, VMWare1 etc.

VMWare0 was set to be bridged and in the combobox of (Bridged to:) there were three options. Two of them are network cards, one for the public communication and one for the private communication inside the datacenter. The third choice which was selected by default was "Automatic". I changed it to stick with the public network card and went back to every VMs network setting and selected Custom instead of Bridged then choose VMWare0.

I think that the old default config somehow got messed up between the two cards. What are your thoughts?

I could've deleted this entire question. But I want people who are going to search about this issue to find a solution plus free points for ya guys.

Cheers,

Phil.
0
Comment
Question by:gxs
1 Comment
 
LVL 119

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 39846678
You should post this solution into the Question, and select it as the Answer for yourself.

and assign yourself 0 points.

e.g.

I solved it.

For every machine, the network selection specified is Bridged.

When I opened the VMWare virtual network editor I found a couple of created connections such as VMware0, VMWare1 etc.

VMWare0 was set to be bridged and in the combobox of (Bridged to:) there were three options. Two of them are network cards, one for the public communication and one for the private communication inside the datacenter. The third choice which was selected by default was "Automatic". I changed it to stick with the public network card and went back to every VMs network setting and selected Custom instead of Bridged then choose VMWare0.

I think that the old default config somehow got messed up between the two cards. What are your thoughts?
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
Esxi management service 10 54
Virtual Machine Consolidation needed status 6 104
Clone VM with existing snapshot via Putty 2 53
convert a NUTANIX VM 3 55
Last article we focus in how to VMware: How to create and use VMs TAGs – Part 1 so before follow this article and perform the next tasks, you should read the first article how to create the TAG before using them in Veeam Backup Jobs.
This article outlines why you need to choose a backup solution that protects your entire environment – including your VMware ESXi and Microsoft Hyper-V virtualization hosts – not just your virtual machines.
This Micro Tutorial walks you through using a remote console to access a server and install ESXi 5.1. This example is showing remote access and installation using a Dell server. The hypervisor is the very first component of your virtual infrastructu…
This video shows you how to use a vSphere client to connect to your ESX host as the root user. Demonstrates the basic connection of bypassing certification set up. Demonstrates how to access the traditional view to begin managing your virtual mac…

777 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