Network connection
in [UK Linux]
|
Prev: AddOn GWK140
Next: sshd known_hosts query
From: dave on 22 Dec 2005 13:06 "Kit" <kit(a)newsgroupsonlysopleasedontemail.com> wrote in message news:43a9e0f0$1_1(a)mk-nntp-2.news.uk.tiscali.com... >> Hmm... Proxy or nameserver settings of some sort? >> >> Can you telnet www.yahoo.co.uk 80 and get an open session? If you can, >> try >> typing GET / in and press return. Does stuff come back ok? >> > > Cannot "telnet www.yahoo.com 80"; it sits there a while, then says "Trying > 1.0.0.0..." then times out. > > Is it time to read about proxies? Hmm... (again). Is "Trying 1.0.0.0..." a literal quote? If that's the case then something is wrong with DNS and I'm a bit confused as to why a ping works. Can you try the following: 1. ping www.yahoo.co.uk You should see it turn into an IP address (I get 217.12.3.11 ATM). 2. Now telnet www.yahoo.co.uk 80 and see what IP it tries. 3. Try /usr/sbin/traceroute -n www.yahoo.co.uk Where does that get to. 4. Try /usr/sbin/traceroute www.yahoo.co.uk Not in numerical mode this time - see if DNS works. If you've said 1.0.0.0 for the sake of brevity and it did indeed try a real IP address but just timed out then this is odd and might be some sort of proxy or port not allowed on the firewall. In this case try telnetting to some other services/ports, for example: telnet mailin-03.mx.aol.com 25 or your ISP POP3 server on 110 Let me know what you find out. Cheers, Dave.
From: Kit on 23 Dec 2005 13:44 "Kit" <kit(a)newsgroupsonlysopleasedontemail.com> wrote in message news:43a9e0f0$1_1(a)mk-nntp-2.news.uk.tiscali.com... >> Hmm... Proxy or nameserver settings of some sort? >> >> Can you telnet www.yahoo.co.uk 80 and get an open session? If you can, >> try >> typing GET / in and press return. Does stuff come back ok? >> > > Cannot "telnet www.yahoo.com 80"; it sits there a while, then says "Trying > 1.0.0.0..." then times out. > > Is it time to read about proxies? --------------------------------------------------------------- Had a day of Xmas duties yesterday! Managed to read a bit about proxy servers on Wikipedia and reverted some vandalism there. Still not much the wiser though. Anyway, here are my responses to your questions & suggestions: >Hmm... (again). Is "Trying 1.0.0.0..." a literal quote? Yes. If that's the case then something is wrong with DNS and I'm a bit confused as to why a ping works. Can you try the following: >1. ping www.yahoo.co.uk >You should see it turn into an IP address (I get 217.12.3.11 ATM). I get 217.12.3.11 also. >2. Now telnet www.yahoo.co.uk 80 >and see what IP it tries. Trying 217.12.3.11... Connected to www.yahoo.co.uk. Escape character is '^]'. (and then after a while of me doing nothing) Connection closed by foreign host. >3. Try /usr/sbin/traceroute -n www.yahoo.co.uk >Where does that get to. groundhog:/home # /usr/sbin/traceroute -n www.yahoo.co.uk traceroute to www.yahoo.co.uk (1.0.0.0), 30 hops max, 40 byte packets 1 192.168.0.1 1.068 ms 0.550 ms 0.542 ms 2 212.74.111.234 15.153 ms 17.680 ms 14.484 ms 3 212.74.106.166 13.940 ms 14.722 ms 14.459 ms 4 212.74.111.130 17.029 ms 19.798 ms 17.539 ms 5 212.74.108.10 19.213 ms 18.076 ms 20.818 ms 6 * 213.200.77.253(N!) 19.588 ms (N!) 18.954 ms >4. Try /usr/sbin/traceroute www.yahoo.co.uk >Not in numerical mode this time - see if DNS works. groundhog:/home # /usr/sbin/traceroute www.yahoo.co.uk traceroute to www.yahoo.co.uk (1.0.0.0), 30 hops max, 40 byte packets 1 mygateway.ar7 (192.168.0.1) 0.668 ms 0.543 ms 0.621 ms 2 lo99.bhm (212.74.111.234) 14.556 ms 16.992 ms 14.671 ms 3 212.74.106.166 16.026 ms 15.490 ms 16.015 ms 4 pos3 (212.74.111.130) 17.479 ms 20.674 ms 16.849 ms 5 pos3 (212.74.108.10) 19.057 ms 41.267 ms 29.464 ms 6 * so (213.200.77.253)(N!) 18.769 ms * >If you've said 1.0.0.0 for the sake of brevity and it did indeed try a real >IP address but just timed out then this is odd and might be some sort of >proxy or port not allowed on the firewall. >In this case try telnetting to some other services/ports, for example: >telnet mailin-03.mx.aol.com 25 >or your ISP POP3 server on 110 chris(a)groundhog:~> telnet pop3.lineone.net 110 Trying 1.0.0.0... telnet: connect to address 1.0.0.0: Connection timed out >Let me know what you find out. >Cheers, >Dave. Many thanks for staying with me on this problem. Kit (Chatham, Kent)
From: dave on 23 Dec 2005 14:03 "Kit" <kit(a)newsgroupsonlysopleasedontemail.com> wrote in message news:43ac40e2$1_1(a)mk-nntp-2.news.uk.tiscali.com... > "Kit" <kit(a)newsgroupsonlysopleasedontemail.com> wrote in message > news:43a9e0f0$1_1(a)mk-nntp-2.news.uk.tiscali.com... >>> Hmm... Proxy or nameserver settings of some sort? >>> >>> Can you telnet www.yahoo.co.uk 80 and get an open session? If you can, >>> try >>> typing GET / in and press return. Does stuff come back ok? >>> >> >> Cannot "telnet www.yahoo.com 80"; it sits there a while, then says >> "Trying >> 1.0.0.0..." then times out. >> >> Is it time to read about proxies? > --------------------------------------------------------------- > Had a day of Xmas duties yesterday! Managed to read a bit about proxy > servers on Wikipedia and reverted some vandalism there. Still not much the > wiser though. > Anyway, here are my responses to your questions & suggestions: > >>Hmm... (again). Is "Trying 1.0.0.0..." a literal quote? > Yes. > > If that's the case then something is wrong with DNS and I'm a bit confused > as to why a ping works. Can you try the following: > Ok - this is a DNS issue I think. <snip successful diagnostics> > >>If you've said 1.0.0.0 for the sake of brevity and it did indeed try a >>real >>IP address but just timed out then this is odd and might be some sort of >>proxy or port not allowed on the firewall. > >>In this case try telnetting to some other services/ports, for example: > >>telnet mailin-03.mx.aol.com 25 > >>or your ISP POP3 server on 110 > > chris(a)groundhog:~> telnet pop3.lineone.net 110 > Trying 1.0.0.0... > telnet: connect to address 1.0.0.0: Connection timed out Ok now this is some sort of weird DNS thing. There's something going wrong which is causing addresses to resolve as 1.0.0.0 but not it seems once you've pinged something. How odd. Can you try: (1) telnet pop3.lineone.net 110 You will presumably just get the 1.0.0.0 and connection timed out. (2) Now ping pop3.lineone.net Does it resolve to an address? If it does then try: (3) telnet pop3.lineone.net 110 And see if it uses the address again and if you get a response. Some other things to try: telnet www.demon.net 80 Does that go to 1.0.0.0 Try wget http://www.demon.net Does that download the page? Try dig www.demon.net What do you get? What is in your /etc/resolv.conf? You might also like to try telnetting into some human-talkable services on other servers such as 80, 110 and 25 (http, pop3 and smtp). POP3 and SMTP give welcome banners so you know you've connected ok. Try some combinations i.e. for server A, ping it then telnet, for B telnet first then if you get 1.0.0.0 try ping then telnet again. > > Many thanks for staying with me on this problem. You're very welcome. Let me know what you find out. Merry Christmas. Cheers, Dave.
From: Alex Monro on 23 Dec 2005 14:20 Kit wrote: > "Kit" <kit(a)newsgroupsonlysopleasedontemail.com> wrote in message > news:43a9e0f0$1_1(a)mk-nntp-2.news.uk.tiscali.com... >>> Hmm... Proxy or nameserver settings of some sort? >>> >>> Can you telnet www.yahoo.co.uk 80 and get an open session? If you can, >>> try >>> typing GET / in and press return. Does stuff come back ok? >>> >> >> Cannot "telnet www.yahoo.com 80"; it sits there a while, then says >> "Trying 1.0.0.0..." then times out. >> >> Is it time to read about proxies? > --------------------------------------------------------------- > Had a day of Xmas duties yesterday! Managed to read a bit about proxy > servers on Wikipedia and reverted some vandalism there. Still not much the > wiser though. > Anyway, here are my responses to your questions & suggestions: > >>Hmm... (again). Is "Trying 1.0.0.0..." a literal quote? > Yes. > > If that's the case then something is wrong with DNS and I'm a bit confused > as to why a ping works. Can you try the following: > >>1. ping www.yahoo.co.uk >>You should see it turn into an IP address (I get 217.12.3.11 ATM). > I get 217.12.3.11 also. > > >>2. Now telnet www.yahoo.co.uk 80 >>and see what IP it tries. > > Trying 217.12.3.11... > Connected to www.yahoo.co.uk. > Escape character is '^]'. > > (and then after a while of me doing nothing) > Connection closed by foreign host. > That is what should happen. > > >>3. Try /usr/sbin/traceroute -n www.yahoo.co.uk >>Where does that get to. > > groundhog:/home # /usr/sbin/traceroute -n www.yahoo.co.uk > traceroute to www.yahoo.co.uk (1.0.0.0), 30 hops max, 40 byte packets > 1 192.168.0.1 1.068 ms 0.550 ms 0.542 ms > 2 212.74.111.234 15.153 ms 17.680 ms 14.484 ms > 3 212.74.106.166 13.940 ms 14.722 ms 14.459 ms > 4 212.74.111.130 17.029 ms 19.798 ms 17.539 ms > 5 212.74.108.10 19.213 ms 18.076 ms 20.818 ms > 6 * 213.200.77.253(N!) 19.588 ms (N!) 18.954 ms > > > >>4. Try /usr/sbin/traceroute www.yahoo.co.uk >>Not in numerical mode this time - see if DNS works. > > groundhog:/home # /usr/sbin/traceroute www.yahoo.co.uk > traceroute to www.yahoo.co.uk (1.0.0.0), 30 hops max, 40 byte packets > 1 mygateway.ar7 (192.168.0.1) 0.668 ms 0.543 ms 0.621 ms > 2 lo99.bhm (212.74.111.234) 14.556 ms 16.992 ms 14.671 ms > 3 212.74.106.166 16.026 ms 15.490 ms 16.015 ms > 4 pos3 (212.74.111.130) 17.479 ms 20.674 ms 16.849 ms > 5 pos3 (212.74.108.10) 19.057 ms 41.267 ms 29.464 ms > 6 * so (213.200.77.253)(N!) 18.769 ms * > This looks reasonable. >>If you've said 1.0.0.0 for the sake of brevity and it did indeed try a >>real IP address but just timed out then this is odd and might be some sort >>of proxy or port not allowed on the firewall. > >>In this case try telnetting to some other services/ports, for example: > >>telnet mailin-03.mx.aol.com 25 > >>or your ISP POP3 server on 110 > > chris(a)groundhog:~> telnet pop3.lineone.net 110 > Trying 1.0.0.0... > telnet: connect to address 1.0.0.0: Connection timed out > Sorry for dissapearing for a bit - had a touch of 'flu. This is _weird_! pop3.lineone.net is _NOT_ 1.0.0.0, it's 212.74.114.58 (unless lineone are doing something _very_ strange with their internal DNS) What does dig tell you the IP for that server is? (I get the following from here: alex(a)finn:~> dig pop3.lineone.net ; <<>> DiG 9.2.2 <<>> pop3.lineone.net ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9330 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;pop3.lineone.net. IN A ;; ANSWER SECTION: pop3.lineone.net. 13172 IN A 212.74.114.58 ;; AUTHORITY SECTION: lineone.net. 3253 IN NS ns0.tiscali.co.uk. lineone.net. 3253 IN NS ns0.as9105.com. ;; ADDITIONAL SECTION: ns0.as9105.com. 120357 IN A 212.139.129.130 ns0.tiscali.co.uk. 98683 IN A 212.74.114.132 ) I guess with tiscali anything's possible! I'm just wondering if lineone do some weird proxying for all the services they support. I think it's theoretically possible they could return different addresses for lookups on their servers to clients coming from inside their network to what they return for external lookups. That would be - unconventional. Another possibility - do you have an /etc/hosts file? Is there anything about pop3.lineone.net in there? Can you connect to www.yahoo.co.uk with a browser? You seem to be able to ping & telnet to it. Can you telnet to port 80 of some of the other sites that you weren't able to access with a browser? Are there any proxies set in your browsers? -- Alex Monro, Exeter, UK Life is like Windows - the documentation alexm at pobox dot com (No HTML) is useless, and it crashes horribly Running on GNU/Linux (SuSE 8.2) from time to time... GPG key 68F8 6270 available from hkp://blackhole.pca.dfn.de
From: Kit on 23 Dec 2005 15:55
> > Ok now this is some sort of weird DNS thing. There's something going wrong > which is causing addresses to resolve as 1.0.0.0 but not it seems once > you've pinged something. How odd. > > Can you try: > > (1) telnet pop3.lineone.net 110 > You will presumably just get the 1.0.0.0 and connection timed out. > > (2) Now ping pop3.lineone.net > Does it resolve to an address? > > If it does then try: > (3) telnet pop3.lineone.net 110 > And see if it uses the address again and if you get a response. > > Some other things to try: > > telnet www.demon.net 80 > Does that go to 1.0.0.0 > > Try wget http://www.demon.net > Does that download the page? > > Try dig www.demon.net > What do you get? > > What is in your /etc/resolv.conf? > > You might also like to try telnetting into some human-talkable services on > other servers such as 80, 110 and 25 (http, pop3 and smtp). POP3 and SMTP > give welcome banners so you know you've connected ok. > > Try some combinations i.e. for server A, ping it then telnet, for B telnet > first then if you get 1.0.0.0 try ping then telnet again. > > I tried most of your suggestions. Transcript of session follows: chris(a)groundhog:~> telnet pop3.lineone.net 110 Trying 1.0.0.0... telnet: connect to address 1.0.0.0: Connection timed out chris(a)groundhog:~> ping pop3.lineone.net PING pop3.lineone.net (212.74.114.58) 56(84) bytes of data. 64 bytes from pop3.lineone.net (212.74.114.58): icmp_seq=1 ttl=60 time=19.3 ms 64 bytes from pop3.lineone.net (212.74.114.58): icmp_seq=2 ttl=60 time=17.1 ms 64 bytes from pop3.lineone.net (212.74.114.58): icmp_seq=3 ttl=60 time=17.0 ms [1]+ Stopped ping pop3.lineone.net chris(a)groundhog:~> telnet pop3.lineone.net 110 Trying 212.74.114.58... Connected to pop3.lineone.net. Escape character is '^]'. +OK POP3 server ready (7.2.052.1) <08382D16BA158CA7A6EE49D9CBBBAC37D65238CC(a)mk-cpfrontend.uk.tiscali.com> quit +OK POP3 server closing connection Connection closed by foreign host. chris(a)groundhog:~> telnet www.demon.net 80 Trying 1.0.0.0... telnet: connect to address 1.0.0.0: Connection timed out chris(a)groundhog:~> wget http://www.demon.net --20:23:53-- http://www.demon.net/ => `index.html.2' Resolving www.demon.net... done. Connecting to www.demon.net[1.0.0.0]:80... failed: Connection timed out. Retrying. --20:27:05-- http://www.demon.net/ (try: 2) => `index.html.2' Connecting to www.demon.net[1.0.0.0]:80... failed: Connection timed out. Retrying. --20:30:16-- http://www.demon.net/ (try: 3) => `index.html.2' Connecting to www.demon.net[1.0.0.0]:80... [2]+ Stopped wget http://www.demon.net chris(a)groundhog:~> dig www.demon.net ; <<>> DiG 9.2.2 <<>> www.demon.net ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49461 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3 ;; QUESTION SECTION: ;www.demon.net. IN A ;; ANSWER SECTION: www.demon.net. 300 IN A 194.159.246.194 ;; AUTHORITY SECTION: www.demon.net. 86400 IN NS ns0.demon.co.uk. www.demon.net. 86400 IN NS ns1.demon.co.uk. www.demon.net. 86400 IN NS ns2.demon.net. ;; ADDITIONAL SECTION: ns0.demon.co.uk. 14400 IN A 158.152.1.65 ns1.demon.co.uk. 14400 IN A 158.152.1.193 ns2.demon.net. 14400 IN A 209.246.126.109 ;; Query time: 2105 msec ;; SERVER: 192.168.0.1#53(192.168.0.1) ;; WHEN: Fri Dec 23 20:32:06 2005 ;; MSG SIZE rcvd: 160 chris(a)groundhog:~> ---------------------------------------------------------------- /etc/resolve.conf (its timestamp is boot-up time today) = ### BEGIN INFO # # Modified_by: dhcpcd # Backup: /etc/resolv.conf.saved.by.dhcpcd # Process: dhcpcd # Process_id: 848 # Script: /sbin/modify_resolvconf # Saveto: # Info: This is a temporary resolv.conf created by service dhcpcd. # The previous file has been saved and will be restored later. # # If you don't like your resolv.conf to be changed, you # can set MODIFY_{RESOLV,NAMED}_CONF_DYNAMICALLY=no. This # variables are placed in /etc/sysconfig/network/config. # # You can also configure service dhcpcd not to modify it. # # If you don't like dhcpcd to change your nameserver # settings # then either set DHCLIENT_MODIFY_RESOLV_CONF=no # in /etc/sysconfig/network/dhcp, or # set MODIFY_RESOLV_CONF_DYNAMICALLY=no in # /etc/sysconfig/network/config or (manually) use dhcpcd # with -R. If you only want to keep your searchlist, set # DHCLIENT_KEEP_SEARCHLIST=yes in /etc/sysconfig/network/dhcp or # (manually) use the -K option. # ### END INFO nameserver 192.168.0.1 ---------------------------------------------------------------- |