It almost seems like both, but I'm no expert and can't tell you for sure. Here's what it does...If I'm on a client windows machine (dhcp served from my dachstein box), and I try to ping or browse www.macys.com, I can't resolve the name. The browser returns w/a "We can't find www.macys.com". Ping from the Windows cmd prompt says "Ping request could not find www.macys.com..." I then ssh to the dachstein box and ping www.macys.com. After a long pause, it returns "PING e108.g.akamaiedge.net (72.246.44.134): 56 data bytes" and pings come back. If I use the IP returned to browse (this is the IP entry I put in the hosts file on my wife's computer for jcrew.com), I can get partial pages, but end up being redirected to www1.macys.com and not able to resolve that. No matter what, I can take any single machine off my network and plug it directly to the cable modem (obviously getting my 1 ip address), and everything browses all 3 of my "problem sites" just fine.
Thanks. mike. Charles Steinkuehler wrote: > Michael McClure wrote: >> I have some wierd problems with my Dachstein box. My wife is not able >> to >> load www.macys.com and www.jcrew.com. She also has problems loading >> images on www.gymboree.com. I'm sure there are others, but these are >> the >> ones she seen so far. One thing it seems they all have in common is >> that >> they all use akamai for something or other -- DNS/Load Balancing, >> edgecaching of images, etc. I fixed jcrew on my wife's computer by >> making >> a host entry in her hosts file that resolves to www.jcrew.com -- but all >> urls on jcrew's site use www. I couldn't fix macys.com the same way >> because there is www.macys.com, www1.macys.com, www2.macys.com, etc and >> even when you ping www.macys.com, a couple different IP's come back. >> >> Does anybody know of anything I can do to fix this? Any help would be >> greatly appreciated. > > First check to see if the issue is with name resolution or talking to > the actual IP address(es). > > IIRC, Dachstein drops traffic from several (at that time) unassigned IP > address ranges, and a number of these have been allocated in recent > years due to general lack of IP addresses (particularly outside the US). > > -- > Charles Steinkuehler > [EMAIL PROTECTED] > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ------------------------------------------------------------------------ > leaf-user mailing list: leaf-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/leaf-user > Support Request -- http://leaf-project.org/ > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
