traceroute and whois not working from VPS.

Traceroute works for me from Atlanta on CentOS 5.3. Don't have whois installed, but I can ping whois.nic.it though.

Both work for me in Fremont. I'd take a look at your firewall settings.

Are you able to ping www.google.com?

@waldo:

Both work for me in Fremont. I'd take a look at your firewall settings.

Are you able to ping www.google.com?

I can ping it but I cannot traceroute it or whois it.

Please help.

Hi,

Definitely take a look at your firewall. Traceroute uses ICMP and high UDP-port probes to do its thing. Maybe try dropping your firewall for a few seconds, do the traceroute, then re-enable your firewall.

–deckert

@Deckert:

Hi,

Definitely take a look at your firewall. Traceroute uses ICMP and high UDP-port probes to do its thing. Maybe try dropping your firewall for a few seconds, do the traceroute, then re-enable your firewall.

–deckert

you are right thanks :)

To save on the headaches I use tcptracroute :wink:

@marcus0263:

To save on the headaches I use tcptracroute :wink:

is there something similar also for whois?

@sblantipodi:

@marcus0263:

To save on the headaches I use tcptracroute :wink:

is there something similar also for whois?
Whois uses tcp or udp already. Make sure you have outgoing port 43 open in your firewall.

@Stever:

@sblantipodi:

@marcus0263:

To save on the headaches I use tcptracroute :wink:

is there something similar also for whois?
Whois uses tcp or udp already. Make sure you have outgoing port 43 open in your firewall.
Better yet just do a "whois" on your own workstation, not your server ;)

Why open another port on your server when you don't need to?

@marcus0263:

@Stever:

@sblantipodi:

is there something similar also for whois?
Whois uses tcp or udp already. Make sure you have outgoing port 43 open in your firewall.
Better yet just do a "whois" on your own workstation, not your server ;)

Why open another port on your server when you don't need to?

Well it's an outgoing port. Seems to me that if you're that concerned about blocking outgoing traffic, then something nasty must be happening inside your VPS. But I could be misunderstanding this discussion….

@sleddog:

@marcus0263:

@Stever:

Whois uses tcp or udp already. Make sure you have outgoing port 43 open in your firewall.
Better yet just do a "whois" on your own workstation, not your server ;)

Why open another port on your server when you don't need to?

Well it's an outgoing port. Seems to me that if you're that concerned about blocking outgoing traffic, then something nasty must be happening inside your VPS. But I could be misunderstanding this discussion….
Nah it's just a case of why open the port when you don't need to? Just do the whois on your workstation