I don't know the answer to solve this problem but just to clearify something above... If you are trying to ping an address over the internet then you do not need to have the same subnet. The only time that you need the same subnet is if you are dealing with LAN base network. I have heard that some ISP (EarthLink, MSN, etc.) have firewall or some kind of blockage to protect their dialup user accounts. Even if the user don't have it on their machine. Hope this information help you out a little. Lite Tech

0

Thank you Jimi, if for nothing else, thank you for knowing the difference between a LAN and the Internet, and not mentioning the subnet. geeez you would think that these guys never used a web browser.... now in the past i have not had problems like this, client wants to set up smaill webserver, I have infact successfully down this in the past, the stranger part is this, if i go to an outside ce, like a site that has an Online Ping utility from there the ping wiill function fine, Both computers are using earthlinks internet service in the same town/city.

0

Norman, What got others going on the subnet mask is that you stated you where trying to "ping" one machine from another. Your wording made it look like you where using a LAN. So basicly what you are saying is if you open a command prompt on the XP box and attempt to ping the other IP address it will just time out and you know the IP you are tying to ping is a valid IP address, correct? I feel Jimi_1 has most likley solved the problem for you already and I would contact the ISP and ask them if they have the blocks in place. Other than trying a different ISP I don't know what to tell you because the problem persist on two different OS platforms which almost rules out it being a software problem. Best of luck, KTTD

0

Earthlink is funny about pinging. Sometime a ping to the internet will work fine, but try pinging any earlink address and most times it'll time out. They're routers are configured not to return a ping.

0

I actually pinged: 158.252.200.116 158.252.200.123 158.252.200.218 successfully around 2:40 am EST on 10-13-02 for what its worth.

0

I don't mean to be smart or sarcastic, but your a professional and have never heard of a ping being refused? Especially after Code Red? I would agree that your ISP is the culprit. Hope this helps or For what is worth,

0

Hey Wolf3d, I am showing those addresses as Sprint dial up in Vegas. I think Earthlink uses UUNET(and a few other small providers) as the major backbone. I resolve Earthlink.net as 207.217.120.207 and that times out on every attempt. I am almost 100% sure at this point that they (Earthlink) are his issue. Jimi_l

0

well well well, who knew that this would be such a hot topic, i will try and answer all of the questions and provide a little more information as to the situation at hand, wcr3d (response 12) Yes, i have heard of isp's blocking a ping, HOWEVER, I have accomplished this very thing, using the same provider (earthlink) on both computers countless times in the past without even so much as a hint of trouble. The trouble only seems to exist between these two particular computers... next, Someone please explain to me how a ping would automatically imply that this was on a LAN and not the internet?? I have been doing this for almost 17 years now and not once have i heard someone say "Ping" and assumed that it was on a LAN versus the internet. Jimi, yes earthlink does use UUNET, however they also use Sprintnet and perhaps in some areas (if its not gone completely)Tymenet. Let me explain a little more about the situation, recently one of the computers was switched from cable access to dialup, the computer had never been configured for dialup access and had not had a modem installed until such time. after several endless nights and days of connecting only to have the connection refused by XP when the computer would attempt to register the computer on the network (Error 720) after finding no resolution for this, and completely losing my patience, i decided to, very literally, rip all of the network information and anything related to it from the registry, expecting this to destroy the OS's functionality (especially seeing as i had also removed all of the backups of the registry) I was surprised to see that when the computer rebooted that the OS actually loaded up and immediately dialed earthlink and connected without kicking itself back out! surprisingly there have not been any other problems with the OS or the network functionality regarding this computer, with the exception that these two machines will not communicate, recently i installed xp on top of itself in the hopes that if there was setting that was missing that it would have been reset and this would all be a distant and soon forgotten ordeal. but of course nothing made by microsoft does what you expect it to do. so here i am. Now that everyone understands that yes, i am completely crazy, and extremely unorthodoxed in my methods, maybe someone out there has seen a similar issue and found resolution or a work around, again i have done this SAME task in the past where both pc's were on earthstink and had no problems at all its not just the ping that is being prevented it is all network traffic, as best i can tell, with the exception of the UDP or TCP connection made by MSN msgner. This has me completely perplexed. to clarify things, the computers and not connected on a lan to each other, one is a stand-alone and the other is connected to a small lan. they both are connecting to the internet using earthlink, they will not allow a ping command nor will they respond to a HTTP GET from each other (mind you they will respond if it comes from a different location), I can successfully ping almost any other sprintnet or earthlink address from both computers. ok well i think that i am going to go stick me head in the oven now, thanks everybody for the input and suggestions. norman.... ... can you say "ouch"...

0

one more thing, other systems, both on and off of the earthstink network and access both machines w/o trouble.... previously one pc, the one on cable at one time(one that i got pissy with), was used as a web server w/o problem for over a year. thanks, norman ... getting a little light headed with my head in this oven....

0

Norm, Neither of your last two posts negate the fact that neither of my two machines have (or had) these issues and I cannot ping any Earthlink address. For example- E:\Documents and Settings\Jim>ping mail.earthlink.net Pinging mail.earthlink.net [207.217.120.208] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 207.217.120.208: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), E:\Documents and Settings\Jim>ping start.earthlink.net Pinging start.earthlink.net [207.217.114.130] with 32 bytes of data: Request timed out. Reply from 207.217.2.125: Destination net unreachable. Request timed out. Request timed out. Ping statistics for 207.217.114.130: Packets: Sent = 4, Received = 1, Lost = 3 (75% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms Using these three different IP's, and every single other one I can find, all do the same thing. Time out or re-direct and then time out. I don't see any other possible problem except the ISP. You hit it on the head when you said the WILL reply from a different location but NOT from each other. I would suspect if you connected any machine you like via Earthlink (dialup) you would have the same result. Why not contact some other Earthlink members (or better still Earthlink tier 2 support) and ask if they get similar results? Jimi_l

0

Jimi, i think that i may have poorly stated or worded the part about getting a response from somewhere else. I believe that you thought i was refering to pinging another provider, for example (ping msn.com blah blah successful result) what i meant was that if i use another tool such as this one found at http://network-tool.com/ from here you can ping the address 158.252.201.67, 168.191.208.206, 63.178.205.234 (even though they resolves to Sprintnet they are earthlink IP's here in Vegas) however i cannot ping the same addresses from my local machine... (NOTE ALL MACHINES PINGED FROM MY MACHINE WERE ON EARTHLINK INCLUDING MINE, however, network-tool.com IS NOT part of the earthlink network but it WILL ping the same addresses, i hope that makes it a little clearer (don't try and ping the mail server at earthlink (207.x.x.x) use the address schemes above, when earthlink users in vegas connect the connect via Sprintnet. incidently, Earthlink Tech support is just as frustrated as you are, however denied knowledge of any block on the sprintet network

0

Ok, If this is the case then would it be safe to assume somthing you "ripped" from the registry hosed the ping protocols from the machine perhaps? Try downloading a program like you used online and see if IT can produce a reply. I have not used any of these but there is a list of them here

0

The Techs at earthlink may be unaware of the blocks, but there could be some kind of Access Control Lists floating around inside the enterprise routers. These lists may keep local traffic from accessing another section. Someday in the past, someone could have decided that no-one from X IP address can access this machine at Y IP address. The IP addresses that you want to access lead to what? I mean, are they servers on the Earthlink network? Are they other dial-up users? Are they router ports? Are they both machines in your house connected only via the earthlin network? You did say that you used to have access in the past, but things have changed now since the cable-modem/dial-up switch. Maybe two computers on the dial-up switch (or whatever they call it) are forbidden to communicate to each other, but when one of them is on cable and the other is on dial-up, everything is OK. I myself pinged 158.252.201.67 from my machine with no problems, so there is something inside of their routers that is blocking YOU. You need to talk to someone with admin access to those routers, not just tech support. Do they use Cisco routers?

0