Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 245
  • Last Modified:

Network connectivity issue with in Windows servers

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
Haribaskaran
Asked:
Haribaskaran
1 Solution
 
HaribaskaranAuthor Commented:
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
 
FdpxAP-GJLCommented:
I assume that even after a reboot the problem still exists. What about reboot of network infrastructure?
0
 
HaribaskaranAuthor Commented:
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
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Tony GiangrecoCommented:
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
 
VirastaRUC Tech Consultant Commented:
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
 
HaribaskaranAuthor Commented:
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
 
tmoore1962Commented:
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
 
HaribaskaranAuthor Commented:
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
 
Tony GiangrecoCommented:
Have you resolved this issue? Any feedback?
0
 
HaribaskaranAuthor Commented:
No the issue still exisits. No resolution found so far.
0
 
HaribaskaranAuthor Commented:
After reconfigure the Port channel between the Blade enclosure and core switch this issue was resolved.
0
 
HaribaskaranAuthor Commented:
No other solution found and finally we did this option with little it outage to production envirnment.
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now