Solved

Network connection issue

Posted on 2009-04-07
4
153 Views
Last Modified: 2012-05-06
Network connection issue

I have 2 windows 2008 servers:

Server1 is is DC
IP=10.35.27.4
SM=255.255.255.0
DG=10.35.27.1
Prefered DNS=10.35.27.4

This server can ping itself, loopback and DG 10.35.27.1
But it cannot ping server 2 (10.35.27.6)
firewall is on

The other server 2 is standalone server it is in a workgroup.
IP=10.35.27.6
SM=255.255.255.0
DG=10.35.27.1
Prefered DNS=10.35.27.4
This server can ping DG 10.35.27.1, can ping 10.35.27.4
firewall is on

From a PC in other subnet that has an IP 10.35.9.3
 I can ping server 1, but can't ping server 2
I can ping DG 10.35.27.1

any idea?

Thanks

 

0
Comment
Question by:jskfan
  • 2
  • 2
4 Comments
 
LVL 8

Accepted Solution

by:
engeltje earned 500 total points
Comment Utility
What we know for sure is that the fault must reside in server 2.
This must be security software blocking the request.

First, try to put the firewall off on server2. Can you ping it now?
In windows firewall, there is an advanced settings-tab. Here you can block echo requests.

If you cannot ping the server with the firewall off, check if there is other security software installed. Security software like Norton can block the requests too.




0
 

Author Comment

by:jskfan
Comment Utility
this is clean installation of Windows 2008 Enterprise edition.
even if I put the firewall off it doesn't resolve the issue.

the only difference that I know of is one copy of windows is 2008 x64 and the other is x86.
I don't think this will be an issue.
and one server is a DC the other not yet, it's a standalone.
Do you think x64 are more tighter in security than x86 ?


0
 
LVL 8

Expert Comment

by:engeltje
Comment Utility
Indeed, you can mix x64 and x32, this wouldn't do anything about the connectivity.
The security for both is the same.

No machine can ping server2 on it's IP. It seems server2 does not accept any incoming traffic at all.

Since there is no firewall or other security software, there must be something wrong with the nic.
Since server2 runs on a x64 OS, the best thing you can check next is the NIC driver.
What NIC do you use? we can check if there is an updated X64 driver available.





0
 

Author Comment

by:jskfan
Comment Utility
If there was a problem with NIC on server 2, do you think it can ping the DG and server 1.
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

Suggested Solutions

I was recently sitting at a desk at work with one of my colleagues and needed some information on my home computer. He watched as I turned on my home computer, established a remote session into it, got the information I needed and then shut it down …
Let’s list some of the technologies that enable smooth teleworking. 
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

771 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

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now