Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

The default gateway is not available.

Posted on 2014-02-09
1
Medium Priority
?
474 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 124

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 2000 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

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

This article will show you how to create an ISO CD-ROM/DVD-ROM image (*.iso), and MD5 checksum signature, for use with VMware vSphere Hypervisor 6.5 (ESXi 6.5). It's a good idea to compare checksums, because many installations fail because of a corr…
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to convert virtaul disk file formats and how to rename virtual machine files on datastores. Open vSphere Web Client: Review VM disk settings: Migrate VM to new datastore with a thick provisioned (lazy zeroed) disk format: Rename a…
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …

876 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