Discussion Locked

Internal nodes ping external IP?

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hey there. My developers tell me that they need to be able to ping external IP addresses because they are trying to create an object on one of our servers for a web application that will be used in house, and by our support techs in the field.
We are currently using Proxy 2.0. In house uses an IP address of 192.168.x.x.
In house can use the internet through Proxy, but cannot ping external IP addresses. Proxy handles all of that.
What can I do to give them what they want without an overhaul of what I have?
Thanks!

15 replies

by erikdr

DON't do that on the production LAN.
If you have installed Proxy that's for a valid reason; what the developers want is more like NAT (Network Address Translation) and that's quite complex to add/replace proxy with.
Point them to one or more specific testing PC's, isolated from the rest of the LAN. When a file has to be transmitted to and from that segment, use a specific procedure - similar to a lock in a canal. Otherwise viruses, untested stuff and all other contents of Pandora's Box creep in and out of your production LAN...

Have fun,

- The Netherlands

by cricket_moon

We do NAT through proxy to a routable IP address. Everyone on the network hits the internet as one IP. What we cannot do is ping anyone outside from a node on the network. This software needs to be able to access our webserver from the network and from the outside world, and kick off an object resting in MTS.
The NAT is there, but how do I allow them to ping an outside IP?

by mctss

There is no way to get past proxy. You are using NAT addressing now and that is what's causing your problem.

The only thing you can do (provided you own enough IP addresses) is to put a node external to proxy. You can attach it directly to the router or CSU/DSU (whatever your demarc is) serving proxy on the WAN side.

by cricket_moon

This is an application, as I stated above, for both internal and external use. I cannot see our support guys walking to anoher computer just to access their calls.

by stillatit

Install the winsock proxy client on the user machine. This is what it is for.

Good luck.

by cricket_moon

We are using winsock proxy client on all of the computers. That's how we can browse the internet at all. Did I miss something in configuring it?

by stillatit

It has been a while since I played with the guts of Proxy, but as recall there are multiple pieces.

What you are probably using is the browser proxy. This requires no installation on your client machines, and simply involves setting the proxy machine's IP or name into the browser on each client.

Separately, there is a winsock proxy. This is a client piece which is explicitly installed on each client machine, where it replaces drivers in the winsock stack with proxy drivers. When it sees a request, it forwards the request to the proxy server. This allows things like PING, standalone FTP, TELNET and so on.

Check your Proxy CD for the install routines and documentation.

Good luck

by cricket_moon

Sorry, but as I stated above, we are using winsock proxy installed on all of the client computers. What I need to know is why it will not allow us to ping outside computers, say from the command line. If I could fix that, the developers would be ok.
Thanks

by ckilday

Have you checked your router or firewall to make sure you're not blocking icmp echo responses? We block ping at our firewall to keep mischief-makers from finding (and attacking) a legitimate address on our network. If you have a protocol analyzer,I'd connect it to your system on both the inside and outside of the firewall/router and see what happens when you try a ping from inside the network. As an alternative, connect to the console port on your router (provided it's a cisco product) and from the enable prompt issue a "debug ip icmp" command. All activity pertaining to icmp will be displayed on your console session. This should point you to the culprit. When you're done with the debug, be sure to issue the "undebug all" command. Debug is very processor intensive and will drag down router performance. Hope this helps. Best wishes.
- ck

by cricket_moon

I have ICMP inbound and out requests open without any hinderance. I can ping proxy's outside IP address from any client. But, I cannot ping any of the web servers' outside IP addresses.
What did I miss in the configuration??

by joshl

A proxy is a layer 7 device. The user
makes the request to the proxy, then the
proxy creates a new request and sends it
out a seperate NIC card. Most proxy
devices only support the HTTP protocol
and occasionally POP3 and SMTP, but I
have never seen one that handles PING.
The Proxy was put into place to restrict
web traffic. If you want to bypass it then
the user will have to set up NAT on the
router, and have a direct line of
communication with the router. Also, ifoutside users want to ping inside, then
static NAT will have to be set up for all
devices inside that will be ping'd. An
alternative is to use NT RAS and create
an IP tunnel through the network.

by cricket_moon

Thanks! At least now I know that it's just the nature of the beast! Setting up NAT on the router may be the best solution possible.

This discussion is closed to new replies.