Can't Ping but CAN RDP?

Hi everyone. I have a network with about three different Windows 2003 Servers Std SP2 and we just added a new file server to our network... Windows server 2003 Standard X64 edition SP2.  I can RDP into this server all I want but my problem is I can't ping it whatsoever from any machine or other server on my network.  If I ping via host name the host name does translate to an IP so I know DNS is working but it times out every time.  If I ping by IP it also times out.  With this problem I can't really map any shares or do much of anything.  Some info that may or may not be of use: We use two subnets... the servers and routers are all on one subnet and users (Macs, PC's and laptops) are on a different subnet,  Can't ping from either.  

Here's what I have tried.

Disabled the Windows Firewall service (even though the firewall is not on), of course rebooted the server, even messed around with turning on the firewall and allowing ICMP requests... still nothing.  (The Windows Firewall is currently not on).  I don't know what else to do.  This is driving me to drink!

Any help is appeciated.
Thanks

Mac
themac2000Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
themac2000Connect With a Mentor Author Commented:
The problem ended up being Symantec's endpoint being installed.  I was not aware that it was installed nor that it contained a firewall/network security tool.  I disabled that and it's fine.  Sorry to bother you all.  

Please close this question
0
 
rjwesleyCommented:
What are the IP's, subnet masks, and gateways for each subnet?

Rob
0
 
TechTiger007Commented:
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
themac2000Author Commented:
Correction: The router is on it's own subnet... subnet 0.  My mistake.
For subnet 1.0
IP of new server      10.10.1.2
IP of another server  10.10.1.1
Gateway                    10.10.0.1
Subnet mask              255.0.0.0

For subnet 2
workstation         10.10.2.123
Gateway and subnet mask are the same as above

Also, one more thing... The new server can ping everyone else.  
0
 
rjwesleyCommented:
Your subnet mask 255.0.0.0 is that a typo?

Rob

0
 
themac2000Author Commented:
Tech Tiger, I looked at that... and ping requests are allowed.  But it shouldn't matter if the firewall service isn't even running.  Or should it?
0
 
themac2000Author Commented:
Rob, no typo.  255.0.0.0 is the subnet mask for this network.  Seemed a little odd to me too having a class A subnet mask in such a small network but I didn't set this one up.  I inherited it.  
0
 
rjwesleyCommented:
Change it to 255.255.255.0 throughout or to whatever you feel you may need in terms of proper subnetting.

Rob
0
 
rjwesleyCommented:
Hold on, this has got me thinking............ because in theory that subnet mask should still work, it's just something not normally done. :)

Rob

How many systems are we talking here? How many routers?
0
 
themac2000Author Commented:
Easily less than 100 PC's.  True it should work... I'm just not sure why they set up a class A scheme with so little machines.  One router.  I'm looking at a possible IP conflict.  I may try changing the IP address of this server to see if that does anything.
0
 
rjwesleyCommented:
255.0.0.0 give you only one subnet...................

If were talking a very minimal amount of connected devices here then I would go to a:

192.168.0.1 - 192.168.0.253 or similiar type of addressing
255.255.255.0 subnet mask
19.168.0.254 (router)

if subnetting is still required then you can probably use 255.255.252.0, which covers all you currently connected devices. To simplify things though you can easily change over to the 192.168 addressing.

Rob (I know I am missing something...)
0
 
PraveenBalasundaramCommented:
Hi,

I had a similar issue, where I can RDP but cannot ping, disabling Symantec End Point did resolve my issue.

 I found it was a windows firewall on the domain network that was turned ON.

Turned OFF windows firewall resolved my issue.

Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.