Linode Forum Index Linode Forum
Linode Community Forums
 


traceroute and whois not working from VPS.

Click here to go to the original topic

 
       Linode Forum Index -> General Discussion
Author Message
sblantipodi



Joined: 13 May 2009
Posts: 450
Location: Italy

Posted: Fri Jun 19, 2009 2:51 pm    Post subject: traceroute and whois not working from VPS.  

Hi,
I have a linode running CentOS 5.3...

When I try to
traceroute a domain name I got this error:
traceroute to mentadent.it (162.61.224.225), 30 hops max, 40 byte packets
send: Operation not permitted

and on whois I got this one:
whois mentadent.it
[Querying whois.nic.it]
[Unable to connect to remote host]


why?
thanks!
Back to top  
Vance



Joined: 18 Jan 2009
Posts: 350

Posted: Sat Jun 20, 2009 12:28 am    Post subject:  

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



Joined: 21 May 2009
Posts: 336

Posted: Sat Jun 20, 2009 12:40 am    Post subject:  

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

Are you able to ping www.google.com?
Back to top  
sblantipodi



Joined: 13 May 2009
Posts: 450
Location: Italy

Posted: Sat Jun 20, 2009 3:22 am    Post subject:  

waldo wrote: 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.
Back to top  
Deckert



Joined: 24 Mar 2007
Posts: 59
Location: South Africa

Posted: Sat Jun 20, 2009 5:21 am    Post subject:  

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
Back to top  
sblantipodi



Joined: 13 May 2009
Posts: 450
Location: Italy

Posted: Sat Jun 20, 2009 12:23 pm    Post subject:  

Deckert wrote: 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 :)
Back to top  
marcus0263



Joined: 21 Jul 2008
Posts: 171
Location: Seattle

Posted: Thu Jun 25, 2009 8:50 pm    Post subject:  

To save on the headaches I use tcptracroute :wink:
Back to top  
sblantipodi



Joined: 13 May 2009
Posts: 450
Location: Italy

Posted: Fri Jun 26, 2009 6:40 am    Post subject:  

marcus0263 wrote: To save on the headaches I use tcptracroute :wink:

is there something similar also for whois?
Back to top  
Stever



Joined: 07 Dec 2007
Posts: 337
Location: NC, USA

Posted: Fri Jun 26, 2009 10:45 am    Post subject:  

sblantipodi wrote: marcus0263 wrote: 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.
Back to top  
marcus0263



Joined: 21 Jul 2008
Posts: 171
Location: Seattle

Posted: Fri Jun 26, 2009 2:31 pm    Post subject:  

Stever wrote: sblantipodi wrote: marcus0263 wrote: 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?
Back to top  
sleddog



Joined: 31 Aug 2008
Posts: 101

Posted: Fri Jun 26, 2009 7:09 pm    Post subject:  

marcus0263 wrote: Stever wrote: sblantipodi wrote: marcus0263 wrote: 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?

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....
Back to top  
marcus0263



Joined: 21 Jul 2008
Posts: 171
Location: Seattle

Posted: Sat Jun 27, 2009 8:50 am    Post subject:  

sleddog wrote: marcus0263 wrote: Stever wrote: sblantipodi wrote: marcus0263 wrote: 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?

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
Back to top  
 
       Linode Forum Index -> General Discussion
Page 1 of 1