Problems connecting to CP
-
I've been having intermittent problems connecting to CP lately. :(( :mad: Today I could not connect from home at all (not even pinging worked), so as a test I logged into my shell account (located somewhere in the US, I forget where exactly), and tried connecting from there, it works, however I got an odd ping response. Notice the lines containing DUP!, it seems that for every ping request, I get 4 responses. One from each web cluster machine perhapse :confused:
/>ping www.codeproject.com
PING www.codeproject.com (207.219.70.31): 48 data bytes
64 bytes from 207.219.70.31: icmp_seq=0 ttl=109 time=74.165 ms
64 bytes from 207.219.70.31: icmp_seq=0 DUP! ttl=109 time=101.666 ms
64 bytes from 207.219.70.31: icmp_seq=0 DUP! ttl=109 time=106.666 ms
64 bytes from 207.219.70.31: icmp_seq=0 DUP! ttl=109 time=109.171 ms
64 bytes from 207.219.70.31: icmp_seq=1 ttl=109 time=72.504 ms
64 bytes from 207.219.70.31: icmp_seq=1 DUP! ttl=109 time=73.335 ms
64 bytes from 207.219.70.31: icmp_seq=1 DUP! ttl=109 time=74.168 ms
64 bytes from 207.219.70.31: icmp_seq=1 DUP! ttl=109 time=74.174 ms
64 bytes from 207.219.70.31: icmp_seq=2 ttl=109 time=71.665 ms
64 bytes from 207.219.70.31: icmp_seq=2 DUP! ttl=109 time=73.335 ms
64 bytes from 207.219.70.31: icmp_seq=2 DUP! ttl=109 time=75.835 ms
64 bytes from 207.219.70.31: icmp_seq=2 DUP! ttl=109 time=76.672 ms
64 bytes from 207.219.70.31: icmp_seq=3 ttl=109 time=71.667 ms
64 bytes from 207.219.70.31: icmp_seq=3 DUP! ttl=109 time=75.835 ms
64 bytes from 207.219.70.31: icmp_seq=3 DUP! ttl=109 time=76.672 ms
64 bytes from 207.219.70.31: icmp_seq=3 DUP! ttl=109 time=77.498 ms
64 bytes from 207.219.70.31: icmp_seq=4 ttl=109 time=71.667 ms
64 bytes from 207.219.70.31: icmp_seq=4 DUP! ttl=109 time=72.502 ms
64 bytes from 207.219.70.31: icmp_seq=4 DUP! ttl=109 time=72.508 ms
64 bytes from 207.219.70.31: icmp_seq=4 DUP! ttl=109 time=73.338 msAlso I resorted to browsing CP using the text mode Links browser, a screenshot of my ordeal[^]. Actually it was not that bad, quite useable actually. :-D Anyway whatever the problem was it now seems to have solved itself :)
Bruce Duncan, CP#9088, CPUA 0xA1EE, Sonork 100.10030
I can levitate -
I've been having intermittent problems connecting to CP lately. :(( :mad: Today I could not connect from home at all (not even pinging worked), so as a test I logged into my shell account (located somewhere in the US, I forget where exactly), and tried connecting from there, it works, however I got an odd ping response. Notice the lines containing DUP!, it seems that for every ping request, I get 4 responses. One from each web cluster machine perhapse :confused:
/>ping www.codeproject.com
PING www.codeproject.com (207.219.70.31): 48 data bytes
64 bytes from 207.219.70.31: icmp_seq=0 ttl=109 time=74.165 ms
64 bytes from 207.219.70.31: icmp_seq=0 DUP! ttl=109 time=101.666 ms
64 bytes from 207.219.70.31: icmp_seq=0 DUP! ttl=109 time=106.666 ms
64 bytes from 207.219.70.31: icmp_seq=0 DUP! ttl=109 time=109.171 ms
64 bytes from 207.219.70.31: icmp_seq=1 ttl=109 time=72.504 ms
64 bytes from 207.219.70.31: icmp_seq=1 DUP! ttl=109 time=73.335 ms
64 bytes from 207.219.70.31: icmp_seq=1 DUP! ttl=109 time=74.168 ms
64 bytes from 207.219.70.31: icmp_seq=1 DUP! ttl=109 time=74.174 ms
64 bytes from 207.219.70.31: icmp_seq=2 ttl=109 time=71.665 ms
64 bytes from 207.219.70.31: icmp_seq=2 DUP! ttl=109 time=73.335 ms
64 bytes from 207.219.70.31: icmp_seq=2 DUP! ttl=109 time=75.835 ms
64 bytes from 207.219.70.31: icmp_seq=2 DUP! ttl=109 time=76.672 ms
64 bytes from 207.219.70.31: icmp_seq=3 ttl=109 time=71.667 ms
64 bytes from 207.219.70.31: icmp_seq=3 DUP! ttl=109 time=75.835 ms
64 bytes from 207.219.70.31: icmp_seq=3 DUP! ttl=109 time=76.672 ms
64 bytes from 207.219.70.31: icmp_seq=3 DUP! ttl=109 time=77.498 ms
64 bytes from 207.219.70.31: icmp_seq=4 ttl=109 time=71.667 ms
64 bytes from 207.219.70.31: icmp_seq=4 DUP! ttl=109 time=72.502 ms
64 bytes from 207.219.70.31: icmp_seq=4 DUP! ttl=109 time=72.508 ms
64 bytes from 207.219.70.31: icmp_seq=4 DUP! ttl=109 time=73.338 msAlso I resorted to browsing CP using the text mode Links browser, a screenshot of my ordeal[^]. Actually it was not that bad, quite useable actually. :-D Anyway whatever the problem was it now seems to have solved itself :)
Bruce Duncan, CP#9088, CPUA 0xA1EE, Sonork 100.10030
I can levitateBruce Duncan wrote: a screenshot of my ordeal[^]. A 404? (slap that puppy! ;P ) :)
I knew it would end badly when I first met Chris in a Canberra alleyway and he said 'try some - it won't hurt you'..... - Christian Graus on Code Project outages A moment of silence please. A programmer's best friend has passed beyond that great exception in the sky.... - Mark Conger on "The coffee machine has died"
-
Bruce Duncan wrote: a screenshot of my ordeal[^]. A 404? (slap that puppy! ;P ) :)
I knew it would end badly when I first met Chris in a Canberra alleyway and he said 'try some - it won't hurt you'..... - Christian Graus on Code Project outages A moment of silence please. A programmer's best friend has passed beyond that great exception in the sky.... - Mark Conger on "The coffee machine has died"
poor puppy! :((
"When the only tool you have is a hammer, a sore thumb you will have."
-
I've been having intermittent problems connecting to CP lately. :(( :mad: Today I could not connect from home at all (not even pinging worked), so as a test I logged into my shell account (located somewhere in the US, I forget where exactly), and tried connecting from there, it works, however I got an odd ping response. Notice the lines containing DUP!, it seems that for every ping request, I get 4 responses. One from each web cluster machine perhapse :confused:
/>ping www.codeproject.com
PING www.codeproject.com (207.219.70.31): 48 data bytes
64 bytes from 207.219.70.31: icmp_seq=0 ttl=109 time=74.165 ms
64 bytes from 207.219.70.31: icmp_seq=0 DUP! ttl=109 time=101.666 ms
64 bytes from 207.219.70.31: icmp_seq=0 DUP! ttl=109 time=106.666 ms
64 bytes from 207.219.70.31: icmp_seq=0 DUP! ttl=109 time=109.171 ms
64 bytes from 207.219.70.31: icmp_seq=1 ttl=109 time=72.504 ms
64 bytes from 207.219.70.31: icmp_seq=1 DUP! ttl=109 time=73.335 ms
64 bytes from 207.219.70.31: icmp_seq=1 DUP! ttl=109 time=74.168 ms
64 bytes from 207.219.70.31: icmp_seq=1 DUP! ttl=109 time=74.174 ms
64 bytes from 207.219.70.31: icmp_seq=2 ttl=109 time=71.665 ms
64 bytes from 207.219.70.31: icmp_seq=2 DUP! ttl=109 time=73.335 ms
64 bytes from 207.219.70.31: icmp_seq=2 DUP! ttl=109 time=75.835 ms
64 bytes from 207.219.70.31: icmp_seq=2 DUP! ttl=109 time=76.672 ms
64 bytes from 207.219.70.31: icmp_seq=3 ttl=109 time=71.667 ms
64 bytes from 207.219.70.31: icmp_seq=3 DUP! ttl=109 time=75.835 ms
64 bytes from 207.219.70.31: icmp_seq=3 DUP! ttl=109 time=76.672 ms
64 bytes from 207.219.70.31: icmp_seq=3 DUP! ttl=109 time=77.498 ms
64 bytes from 207.219.70.31: icmp_seq=4 ttl=109 time=71.667 ms
64 bytes from 207.219.70.31: icmp_seq=4 DUP! ttl=109 time=72.502 ms
64 bytes from 207.219.70.31: icmp_seq=4 DUP! ttl=109 time=72.508 ms
64 bytes from 207.219.70.31: icmp_seq=4 DUP! ttl=109 time=73.338 msAlso I resorted to browsing CP using the text mode Links browser, a screenshot of my ordeal[^]. Actually it was not that bad, quite useable actually. :-D Anyway whatever the problem was it now seems to have solved itself :)
Bruce Duncan, CP#9088, CPUA 0xA1EE, Sonork 100.10030
I can levitateIs DUP like DOH ? :P ( I'm presuming it means duplicate... ) Christian No offense, but I don't really want to encourage the creation of another VB developer. - Larry Antram 22 Oct 2002 Hey, at least Logo had, at it's inception, a mechanical turtle. VB has always lacked even that... - Shog9 04-09-2002 Again, you can screw up a C/C++ program just as easily as a VB program. OK, maybe not as easily, but it's certainly doable. - Jamie Nordmeyer - 15-Nov-2002
-
I've been having intermittent problems connecting to CP lately. :(( :mad: Today I could not connect from home at all (not even pinging worked), so as a test I logged into my shell account (located somewhere in the US, I forget where exactly), and tried connecting from there, it works, however I got an odd ping response. Notice the lines containing DUP!, it seems that for every ping request, I get 4 responses. One from each web cluster machine perhapse :confused:
/>ping www.codeproject.com
PING www.codeproject.com (207.219.70.31): 48 data bytes
64 bytes from 207.219.70.31: icmp_seq=0 ttl=109 time=74.165 ms
64 bytes from 207.219.70.31: icmp_seq=0 DUP! ttl=109 time=101.666 ms
64 bytes from 207.219.70.31: icmp_seq=0 DUP! ttl=109 time=106.666 ms
64 bytes from 207.219.70.31: icmp_seq=0 DUP! ttl=109 time=109.171 ms
64 bytes from 207.219.70.31: icmp_seq=1 ttl=109 time=72.504 ms
64 bytes from 207.219.70.31: icmp_seq=1 DUP! ttl=109 time=73.335 ms
64 bytes from 207.219.70.31: icmp_seq=1 DUP! ttl=109 time=74.168 ms
64 bytes from 207.219.70.31: icmp_seq=1 DUP! ttl=109 time=74.174 ms
64 bytes from 207.219.70.31: icmp_seq=2 ttl=109 time=71.665 ms
64 bytes from 207.219.70.31: icmp_seq=2 DUP! ttl=109 time=73.335 ms
64 bytes from 207.219.70.31: icmp_seq=2 DUP! ttl=109 time=75.835 ms
64 bytes from 207.219.70.31: icmp_seq=2 DUP! ttl=109 time=76.672 ms
64 bytes from 207.219.70.31: icmp_seq=3 ttl=109 time=71.667 ms
64 bytes from 207.219.70.31: icmp_seq=3 DUP! ttl=109 time=75.835 ms
64 bytes from 207.219.70.31: icmp_seq=3 DUP! ttl=109 time=76.672 ms
64 bytes from 207.219.70.31: icmp_seq=3 DUP! ttl=109 time=77.498 ms
64 bytes from 207.219.70.31: icmp_seq=4 ttl=109 time=71.667 ms
64 bytes from 207.219.70.31: icmp_seq=4 DUP! ttl=109 time=72.502 ms
64 bytes from 207.219.70.31: icmp_seq=4 DUP! ttl=109 time=72.508 ms
64 bytes from 207.219.70.31: icmp_seq=4 DUP! ttl=109 time=73.338 msAlso I resorted to browsing CP using the text mode Links browser, a screenshot of my ordeal[^]. Actually it was not that bad, quite useable actually. :-D Anyway whatever the problem was it now seems to have solved itself :)
Bruce Duncan, CP#9088, CPUA 0xA1EE, Sonork 100.10030
I can levitateI'm having a terrible time trying to connect as well. I'm considering going outside. Bruce Duncan wrote: a screenshot of my ordeal Wow, that's much better than I would expect for a text-mode browser. It's not pretty, but it certainly is useable.
"What do you want to do tonight, Bill?"
"Same thing we do every night, Steve. Try to take over the world!" -
I'm having a terrible time trying to connect as well. I'm considering going outside. Bruce Duncan wrote: a screenshot of my ordeal Wow, that's much better than I would expect for a text-mode browser. It's not pretty, but it certainly is useable.
"What do you want to do tonight, Bill?"
"Same thing we do every night, Steve. Try to take over the world!"Daniel Ferguson wrote: I'm considering going outside. Don't do it!!!! Trust me, I've been out there... verrrryy scary place!:~ "My child was Inmate of the Month at Mohave County Jail" - Bumper Sticker in Bullhead City, AZ
-
I've been having intermittent problems connecting to CP lately. :(( :mad: Today I could not connect from home at all (not even pinging worked), so as a test I logged into my shell account (located somewhere in the US, I forget where exactly), and tried connecting from there, it works, however I got an odd ping response. Notice the lines containing DUP!, it seems that for every ping request, I get 4 responses. One from each web cluster machine perhapse :confused:
/>ping www.codeproject.com
PING www.codeproject.com (207.219.70.31): 48 data bytes
64 bytes from 207.219.70.31: icmp_seq=0 ttl=109 time=74.165 ms
64 bytes from 207.219.70.31: icmp_seq=0 DUP! ttl=109 time=101.666 ms
64 bytes from 207.219.70.31: icmp_seq=0 DUP! ttl=109 time=106.666 ms
64 bytes from 207.219.70.31: icmp_seq=0 DUP! ttl=109 time=109.171 ms
64 bytes from 207.219.70.31: icmp_seq=1 ttl=109 time=72.504 ms
64 bytes from 207.219.70.31: icmp_seq=1 DUP! ttl=109 time=73.335 ms
64 bytes from 207.219.70.31: icmp_seq=1 DUP! ttl=109 time=74.168 ms
64 bytes from 207.219.70.31: icmp_seq=1 DUP! ttl=109 time=74.174 ms
64 bytes from 207.219.70.31: icmp_seq=2 ttl=109 time=71.665 ms
64 bytes from 207.219.70.31: icmp_seq=2 DUP! ttl=109 time=73.335 ms
64 bytes from 207.219.70.31: icmp_seq=2 DUP! ttl=109 time=75.835 ms
64 bytes from 207.219.70.31: icmp_seq=2 DUP! ttl=109 time=76.672 ms
64 bytes from 207.219.70.31: icmp_seq=3 ttl=109 time=71.667 ms
64 bytes from 207.219.70.31: icmp_seq=3 DUP! ttl=109 time=75.835 ms
64 bytes from 207.219.70.31: icmp_seq=3 DUP! ttl=109 time=76.672 ms
64 bytes from 207.219.70.31: icmp_seq=3 DUP! ttl=109 time=77.498 ms
64 bytes from 207.219.70.31: icmp_seq=4 ttl=109 time=71.667 ms
64 bytes from 207.219.70.31: icmp_seq=4 DUP! ttl=109 time=72.502 ms
64 bytes from 207.219.70.31: icmp_seq=4 DUP! ttl=109 time=72.508 ms
64 bytes from 207.219.70.31: icmp_seq=4 DUP! ttl=109 time=73.338 msAlso I resorted to browsing CP using the text mode Links browser, a screenshot of my ordeal[^]. Actually it was not that bad, quite useable actually. :-D Anyway whatever the problem was it now seems to have solved itself :)
Bruce Duncan, CP#9088, CPUA 0xA1EE, Sonork 100.10030
I can levitateBruce Duncan wrote: Also I resorted to browsing CP using the text mode Links browser :omg: :cool: !!
David Wulff http://www.davidwulff.co.uk
David Wulff Born and Bred.
-
Daniel Ferguson wrote: I'm considering going outside. Don't do it!!!! Trust me, I've been out there... verrrryy scary place!:~ "My child was Inmate of the Month at Mohave County Jail" - Bumper Sticker in Bullhead City, AZ
-
Bruce Duncan wrote: a screenshot of my ordeal[^]. A 404? (slap that puppy! ;P ) :)
I knew it would end badly when I first met Chris in a Canberra alleyway and he said 'try some - it won't hurt you'..... - Christian Graus on Code Project outages A moment of silence please. A programmer's best friend has passed beyond that great exception in the sky.... - Mark Conger on "The coffee machine has died"
Megan Forbes wrote: A 404? Worked for me when I posted :confused: still does more :confused: Megan Forbes wrote: slap that puppy! Nah, we're nice guys :-)
Bruce Duncan, CP#9088, CPUA 0xA1EE, Sonork 100.10030
I can levitate birds... -
I'm having a terrible time trying to connect as well. I'm considering going outside. Bruce Duncan wrote: a screenshot of my ordeal Wow, that's much better than I would expect for a text-mode browser. It's not pretty, but it certainly is useable.
"What do you want to do tonight, Bill?"
"Same thing we do every night, Steve. Try to take over the world!"Daniel Ferguson wrote: going outside Go.... Outside.... :confused: ... Oh! You must mean the big blue room! ;)
Bruce Duncan, CP#9088, CPUA 0xA1EE, Sonork 100.10030
I can levitate birds...
