Solved

Network connectivity issue with in Windows servers

Posted on 2013-06-02
12
237 Views
Last Modified: 2013-08-07
Hi,

I am facing weird problem in my network environment.

I have windows 2008 single forest & domain model. Having windows 203 & 2008 servers all are in the same data center and same network(same subnet mask). For the last 2 months I m facing the problem as from the server A- 192.168.0.23 unable to connect B -192.168.0.35.

Gateway 192.168.0.1

when I try to ping server B from Server A it is giving the error as


ping server B

Pinging 192.168.0.35 with 32 bytes of data:
Reply from 192.168.0.23: Destination host unreachable.


But from the server B, I am able to connect Server A. but from the both servers I can able to connect other servers. Only Server A having the issue with B. there is no other issue.

Some one can you help on this. Where it went wrong?
0
Comment
Question by:Haribaskaran
12 Comments
 

Author Comment

by:Haribaskaran
ID: 39215263
By default firewall in OS has been disabled in all servers. All the servers are in the same data center. there is no firewall in between them. It was working well earlier.
0
 
LVL 6

Expert Comment

by:FdpxAP-GJL
ID: 39215346
I assume that even after a reboot the problem still exists. What about reboot of network infrastructure?
0
 

Author Comment

by:Haribaskaran
ID: 39215398
Yes. I have rebooted both servers. still same issue. But Network side we havenot done any reboot since it involved lot of outage for other production servers.
0
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 
LVL 25

Expert Comment

by:Tony Giangreco
ID: 39215477
If they are both DC's, run the Repadmin /showrepl commands and make sure replication runs properly.

http://technet.microsoft.com/en-us/library/cc742066(v=ws.10).aspx

If they are not both DC's, on the 1st server, edit the host file and add the 2nd server's IP and name. Then edit the host file on the 2nd server and add the IP and name of the 1st server.

This has worked for me in the past.
0
 
LVL 9

Expert Comment

by:VirastaR
ID: 39215935
Hi,

Based on your description it seems only like firewall issue.

Server A -> Server B = Not Working
Server B -> Server A = Working

The Servers hosted in a physical servers or on VMs?

Can you please check firewall once again in Server A and also check whether IPv6 is enabled,if not used please disable IPv6 and check again.

Let me know :)
0
 

Author Comment

by:Haribaskaran
ID: 39216818
Confirmed the firewall has been disabled.

Server A is VM and Server B is physical.

I installed the netmon in both servers and started capturing the packets. Now i can able to connect Server B from server A. Not sure netmon did some magic. But still the same issue in other servers there this netmon trick not worked. I beleive something strange.
0
 
LVL 10

Expert Comment

by:tmoore1962
ID: 39216846
Since 1 is a VM and the other physical, I would look at the VM's virtural switch or router configuration.  If you do a Tracert from one to the other where does the trace stop??  Depending on your VM host the VM switch can be configured for VM network access only, VM network to VM host access only, or VM network to LAN network access.
0
 

Author Comment

by:Haribaskaran
ID: 39216900
Here the outout I am getting to try to tracert from server A
G:\>tracert server B

Tracing route to SerevrB.XXXXX.org [192.168.0.35]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2

from Server B to Server A tracert result is

G:\>tracert ServerA

Tracing route to serverA.XXXXXX.org [192.168.0.23]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  serverA.XXXXX.org [192.168.0.23]

Trace complete.
0
 
LVL 25

Expert Comment

by:Tony Giangreco
ID: 39300151
Have you resolved this issue? Any feedback?
0
 

Author Comment

by:Haribaskaran
ID: 39303498
No the issue still exisits. No resolution found so far.
0
 

Accepted Solution

by:
Haribaskaran earned 0 total points
ID: 39378754
After reconfigure the Port channel between the Blade enclosure and core switch this issue was resolved.
0
 

Author Closing Comment

by:Haribaskaran
ID: 39388631
No other solution found and finally we did this option with little it outage to production envirnment.
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

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

On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
When you upgrade from Windows 8 to 8.1 or to Windows 10 or if you are like me you are on the Insider Program you may find yourself with many 450MB recovery partitions.  With a traditional disk that may not be a problem but with relatively smaller SS…
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

856 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