You need to put an 80 after the telnet so something like telnet mycompany.org 80
the 80 gives you the correct port number. On Jan 19, 2011, at 1:48 PM, Geoff Waaler wrote: > Thanks much for the suggestion Andre, > > I reset my DLink 655 to factory defaults and confirmed that it is indeed set > to DHCP. When I attempt to telnet to > "http://nightly.webkit.org";, it times out Trying: 208.68.139.89 > > Needless to say nothing happens when I click on the "download the latest > nightly build" link from webkit.org. As noted before all attempts to check > for updates appear to time out and issue the error message documented > initially. > > When I ping the address from windows I receive a reply from a different IP > "208.68.143.55", though it also hangs when I attempt to enter that URL from > either Mozilla or MSIE. > > The problem disappears when I remove the router and connect directly to my > cable modem. Very strange since until recently I had no problems while > attached wirelessly via my DLink 655. > > Except for the fact that my problem is with access to the webkit site, this > is really a network issue, hence is probably OT here. Perhaps if anyone is > willing to help you can write me privately, and I will post the solution here > in case anyone is curious (assuming I find a solution that is). > > Best regards. > Geoff > > > On Jan 19, 2011, at 7:12 AM, Andre Nuno Soares wrote: > >> Hello Geoff , >> >> Check your DNS configuration. >> Did you set it manually? If so, change it to DHCP and see if it helps. >> >> Also, what happens if you do a telnet to the webkit address from the >> terminal? >> >> >> HTH, >> André >> >> On 18-01-2011 18:23, Geoff Waaler wrote: >>> Okay, I am officially replying to my own post. It's a long story, but to >>> reduce it to the relevant facts, I am able to update webkit when I attach >>> my MBP directly to the cable modem via eathernet. When routers are >>> introduced into the circuit, however, I always experience the symptoms >>> described below. I've seen this both with my Mother's Linksys router and >>> my d-link DIR655 which are both at the latest available firmware levels. >>> There is no filtering configured on either router, and until late December >>> I had no problems updating webkit from either location. >>> >>> While visiting the Apple store I had no difficulty updating Webkit using >>> their hotspot, hence I presume there must be a way to accomplish the task >>> through routers<smile>. More over, I wouldn't be the only one posting on >>> this. >>> >>> To reitterate, I have no web filtering active on either device, and as far >>> as I know, only the webkit download and update check sites are affected. >>> Any suggestions would be greatly appreciated! >>> >>> Geoff >>> >>> On Jan 13, 2011, at 1:03 PM, Geoff Waaler wrote: >>> >>>> Greetings, >>>> >>>> I'm having varied symptoms browsing on my MBP. Perhaps the two are >>>> related -- I'm guessing so. It all started when Webkit randomly hung up. >>>> I would press the submit button in a form and then Voiceover would >>>> repeatidly announce "safari busy" and "safari ready". Pressing a key did >>>> not take and I had to close and reopen the browser. >>>> >>>> Next, I was unable to update Webkit. Since that problem appeared to be >>>> unique to me I erased webkit.app and attempted to download the current >>>> build. For several days now I click on the download link and after about >>>> 30 seconds I receive the following message: >>>> >>>> Safari can’t open the page “http://nightly.webkit.org/” because the server >>>> where this page is located isn’t responding. >>>> >>>> I can't load that URL on my XP machine either, but can't imagine that my >>>> ISP is blocking it? I'm also having problems displaying other pages. For >>>> example, I'm attempting to register at the Apple developer site and it >>>> hangs after I press submit. >>>> >>>> I killed my cookies, but this had no affect. Could not find how to clear >>>> any other cache that could be a factor? >>>> >>>> Is it time to reinstall Snow leopard? Btw, version 10.6.7 is installed, >>>> but my problem began before this update was available. >>>> >>>> TIA for any suggestions. >>>> Geoff >> >> -- >> You received this message because you are subscribed to the Google Groups >> "MacVisionaries" group. >> To post to this group, send email to macvisionaries@googlegroups.com. >> To unsubscribe from this group, send email to >> macvisionaries+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/macvisionaries?hl=en. >> > > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To post to this group, send email to macvisionaries@googlegroups.com. > To unsubscribe from this group, send email to > macvisionaries+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/macvisionaries?hl=en. -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To post to this group, send email to macvisionaries@googlegroups.com. To unsubscribe from this group, send email to macvisionaries+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en.
