What does it mean when I can go to in Internet Explorer, but if I go to the cmd.exe prompt and ping I get back 4x no response packets?
How can you have both?
How can you have both?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
I can view the internet but I can't ping anything!
- Thread starter tjtindal
- Start date
Serbtastic
Vendor
It means the web server hosting is configured to not respond to ping (ICMP) packets. This is a common scenario found on the internet.
- Thread starter
- #3
Okay, let me be more specific. I'm working on repairing a friend of mine's computer for his business, and he orders parts through a website called Agco. I can use his internet explorer to access Agco's website, but the program used for ordering parts is having a port error problem when trying to access the website.
In addition to that, I can hit their website through IE, but I can't ping it. I figured me being able to ping it was a good start, but I can't even do that.
So, updated question: For internet access in general, not specifically for any website in particular, how is it possible that you can hit a website with IE but not be able to ping it from cmd.exe? Any website, any one at all.
In addition to that, I can hit their website through IE, but I can't ping it. I figured me being able to ping it was a good start, but I can't even do that.
So, updated question: For internet access in general, not specifically for any website in particular, how is it possible that you can hit a website with IE but not be able to ping it from cmd.exe? Any website, any one at all.
- Thread starter
- #5
The ordering program is attempting to hit ip address: 208.255.231.102 through port 900. They've also tried ports 23, 3001, 3002 and 9021.
They are indeed behind a firewall, and the program takes that into consideration making the user have a Firewall ID typed in. Hope this helps.
They are indeed behind a firewall, and the program takes that into consideration making the user have a Firewall ID typed in. Hope this helps.
Are you talking about the Agco firewall? Even if your friend has to authenticate to the firewall with an ID, those ports still have to be open on the firewall for the program to succeed.
What I am asking is do YOU have a firewall, also? If your machine is windows XP, has the built-in firewall gotten turned on? Has your friend's place of business added a firewall?
Have you contacted the company? What ports do they tell you to use?
What I am asking is do YOU have a firewall, also? If your machine is windows XP, has the built-in firewall gotten turned on? Has your friend's place of business added a firewall?
Have you contacted the company? What ports do they tell you to use?
- Thread starter
- #7
- Thread starter
- #9
If you are trying to telnet to those ports on the remote computer, those ports do not need to be open on your firewall. Open ports are generally for incoming session establishment, not outgoing sessions.
Web browsers use the HTTP protocol on TCP/IP, where ping uses the ICMP protocol on IP, so it is very possible that ICMP requests or replies will be blocked somewhere along the route, but web browsing would work without an issue.
If you are trying to see if ping will work for you, try "ping because they do reply.
It appears that you are using Windows for your OS, but I am not sure which version. If it is XP or Vista, then it is possible that you have a software firewall on the PC itself (built-in, Norton, McAfee, etc.) that may well be dropping ICMP packets. I'd check that first. You may also have a router and/or firewall that could be affecting your ability to connect to this server (or application). And the other end could have a firewall and/or router that is blocking your incoming connection. But, since they are recommending alternative methods of connecting with them, it seems likely that their firewall/router configuration is designed to let you connect.
How were you testing ports 23, 3001, 3002, and 9021? Were you telnetting to them manually or using the web browser?
You may also want to install Wireshark on your system so that you can capture packets to/from your PC to help you troubleshoot the problem.
pansophic
Web browsers use the HTTP protocol on TCP/IP, where ping uses the ICMP protocol on IP, so it is very possible that ICMP requests or replies will be blocked somewhere along the route, but web browsing would work without an issue.
If you are trying to see if ping will work for you, try "ping because they do reply.
It appears that you are using Windows for your OS, but I am not sure which version. If it is XP or Vista, then it is possible that you have a software firewall on the PC itself (built-in, Norton, McAfee, etc.) that may well be dropping ICMP packets. I'd check that first. You may also have a router and/or firewall that could be affecting your ability to connect to this server (or application). And the other end could have a firewall and/or router that is blocking your incoming connection. But, since they are recommending alternative methods of connecting with them, it seems likely that their firewall/router configuration is designed to let you connect.
How were you testing ports 23, 3001, 3002, and 9021? Were you telnetting to them manually or using the web browser?
You may also want to install Wireshark on your system so that you can capture packets to/from your PC to help you troubleshoot the problem.
pansophic
Serbtastic
Vendor
Also, what is the exact error you get when trying ports 900, 23 etc?
Interesting. Ping/ICMP messages can be shut off for concern/security reasons.
You can test if your friends computer is even reaching the distant end by typing (at the command prompt)
telnet [site name or IP] 23
If you get "connecting" and aren't kicked back to the command prompt rather quickly, you have a direct line to port 23. Repeat with all the ports. If you get kicked back with an error, there could be a bunch of reasons for it.
As far as answering you original question, browsers can cache webpages, and update them only as needed. Best bet would be to clear history, and delete your temporary internet files. If you have issues "getting" to web sites, you now know that there may be an issue internally on the network (to include the workstation you attempted from).
You can test if your friends computer is even reaching the distant end by typing (at the command prompt)
telnet [site name or IP] 23
If you get "connecting" and aren't kicked back to the command prompt rather quickly, you have a direct line to port 23. Repeat with all the ports. If you get kicked back with an error, there could be a bunch of reasons for it.
As far as answering you original question, browsers can cache webpages, and update them only as needed. Best bet would be to clear history, and delete your temporary internet files. If you have issues "getting" to web sites, you now know that there may be an issue internally on the network (to include the workstation you attempted from).
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question