We help IT Professionals succeed at work.

Can't ping to the SBS 2003 on  virtual machine.

YasuYasu
YasuYasu asked
on
555 Views
Last Modified: 2012-02-09
Hi Experts,

I have a problem with our sbs 2003 server running on virtual machine.

The sbs2003 went to down yesterday so forced to start up this morning but can't receive emails, can't access webmail can't  login to the domain as well.

The server is unable to access to external network as well as internal network which means that I can't ping from my window7 (192.168.1.61) to the server (192.168.1.10) and of course from the server to my machine can't be pinged.

Tried from another PC (192.168.1.73) to the server but still no luck. the server was pingable until yesterday.

I thought something wrong to firewall on the server but as the server has only one nic  it is not related to the problem.

Can someone help me to solve this problem? I want to make ping-able internally for now.

Thanks.

YasuYasu
Comment
Watch Question

JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
Did the network mode change from Bridged to NAT on the restart?  
... Thinkpads_User

Author

Commented:
No I didn't change it.  But it has been NAT.
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
>>> can't ping from my window7 (192.168.1.61) to the server (192.168.1.10)

If the network mode has been NAT, then I would expect the server to be on a different subnet. So the above does not make sense.

Try changing the network mode of the virtual machine to Bridged.  ... Thinkpads_User
Jer

Commented:
Are you sure that the NIC settings are correct?  With your symptoms, it really sounds like either your NIC settings are hosed or there is another device on the network with the same IP.

Author

Commented:
both you guys,

Sorry, my answer wasn't clear.
I have attached a pic for our network. it is basically same and the sbs2003 (192.168.1.10) is  running on vmware ESXi 4.1 on HP server and I am trying to ping from one of client computers (192.168.1.61).

The network is configured as NAT ( the virtual instance can't be changed to bridge on ESXi can it?) and I can confirm that there is no other device as same IP with the server.

Maybe something wrong with ESXi?

I have missed to attach a pic. here you go.
lan.jpg
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
NAT and Bridged are terms applying to the virtual network card on your virtual machine. It probably is already set to Bridged, but pleased do check it out in your virtual machine settings.

Perhaps because of the shutdown, TCP/IP has a problem. Look at this Microsoft article to reset TCP/IP on Server 2003

http://support.microsoft.com/kb/317518

.... Thinkpads_User

Author

Commented:
Thinkpads_User

Thanks. I have tried reset TCP/IP didn't work and would like to check the bride, but couldn't figure out how on esxi 4.1. coulc you let me know how to do?

Thanks.
Business Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Thinkpads_User<br /><br />In the end, I rebooted the server and it started working.  I don't know why but TCP/IP restore worked. <br /><br />Thanks<br />YasuYasu
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Commented:
Thank you. I was pleased to assist and glad it is working for you. ... Thinkpads_User
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.