Solved

Can't Ping but CAN RDP?

Posted on 2008-10-08
12
763 Views
Last Modified: 2012-08-27
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
0
Comment
Question by:themac2000
12 Comments
 
LVL 8

Expert Comment

by:rjwesley
ID: 22672002
What are the IP's, subnet masks, and gateways for each subnet?

Rob
0
 
LVL 13

Expert Comment

by:TechTiger007
ID: 22672202
0
 

Author Comment

by:themac2000
ID: 22672249
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
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 8

Expert Comment

by:rjwesley
ID: 22672283
Your subnet mask 255.0.0.0 is that a typo?

Rob

0
 

Author Comment

by:themac2000
ID: 22672286
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
 

Author Comment

by:themac2000
ID: 22672317
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
 
LVL 8

Expert Comment

by:rjwesley
ID: 22672349
Change it to 255.255.255.0 throughout or to whatever you feel you may need in terms of proper subnetting.

Rob
0
 
LVL 8

Expert Comment

by:rjwesley
ID: 22672593
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
 

Author Comment

by:themac2000
ID: 22672747
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
 
LVL 8

Expert Comment

by:rjwesley
ID: 22672850
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
 

Accepted Solution

by:
themac2000 earned 0 total points
ID: 22734648
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
 

Expert Comment

by:PraveenBalasundaram
ID: 38339350
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

Featured Post

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.

Question has a verified solution.

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

Suggested Solutions

Organizations create, modify, and maintain huge amounts of data to help their businesses earn money and generally function.  Typically every network user within an organization has a bit of disk space to store in process items and personal files.   …
Numerous times I have been asked this questions that what is it that makes my machine log on so slow, there have been cases where computers took 23 minute exactly after taking password and getting to the desktop. Interesting thing was the fact th…
Along with being a a promotional video for my three-day Annielytics Dashboard Seminor, this Micro Tutorial is an intro to Google Analytics API data.
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

816 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

13 Experts available now in Live!

Get 1:1 Help Now