A case of Epic beer to the first person...

   Previous             - Browse archive             Next    

None

NIKON D70 - 1/320 sec, f5 at 44mm

I'll buy a case of Epic beer to the first person* that can solve my networking problem at home, (special conditions apply of course).

I have a Debian server on one end of my desk that hosts this website and a PC at the other end of my desk that I'm writing this on now. The web server happily serves pages to the outside world ok but takes 4 minutes to serve a page on my internal network. They are both connected to the same switch.

The network is fine because Synergy works perfectly between the PC and the server. Transferring files between them is perfect. But either apache or PHP or MySQL is causing very slow page lad times.

DNS appears fine. The server is not loaded. No IO issues and no swapping.

Any suggestions of where to look, anyone?

Bloody hell I hate computers. They completely give me the shits.

The Photo

It's our shadow somewhere over the Waikato from our flight on Saturday afternoon.

*You have to collect the beer, I cannot ship it.

Post Meta

Posted: Wednesday, 19 September, 2007 18:43

Captured: 2007:09:15 14:05:59

Add your own comment

  • I won't help for Epic beer. You wanna change the brand? So how do you connect to the server, whats the domainname and to what does it resolve? Is it the external IP? Did you do some tracerting?
    Olly - Wednesday, 19 September, 2007 21:56
  • Server is on the same switch as PC, domainname is www.spudooli.com and I have that along with it's private IP address in my hosts file. Never throught to do a traceroute. Both devices are on my internal network
    Dave - Wednesday, 19 September, 2007 22:01
  • I suggest you comment the entry in your hosts file, flush the dns on your pc and see what happens. Good luck! How do you rate Epic beer, mate?
    Jody - Thursday, 20 September, 2007 3:40
  • Two stupid questions that you've possibly already tried: 1. It's very easy for people who think about software all day to entirely forget about hardware. Have you checked the switchport and cable to your internal PC and its NIC? 2. Have you turned up the loglevel to debug in apache to see what is happening at a low level when you request a page internally? Oh, and a third question: You clearly have excellent taste in beer (it seems Epic is going almost mainstream now, good on it, couldn't happen to a nicer beer) - have you considered joining SOBA? I'd post a link but your blog might think I'm a spammer rather than a passionate beer advocate. ;) www dot soba dot org dot nz. You know you want to.
    Greig - Thursday, 20 September, 2007 8:14
  • Make sure reverse DNS lookup either (a) works, or (b) is turned off in the Apache config. Docs: http://httpd.apache.org/docs/2.2/mod/core.html#hostnamelookups
    Rob - Thursday, 20 September, 2007 9:14
  • apt-get install mtr mtr your-pc-hostname then try route it will be your dns resolv setup broke, cat /etc/resolv.conf
    jamesh - Thursday, 20 September, 2007 9:35
  • stop hosting that stuff AT HOME and move it to somewhere we can really take care of it. That will solve your problems. That'll be one case of epic, thanks.
    Mike - Thursday, 20 September, 2007 10:44
  • Given that none of the comments above solve your problem and are clearly not beer worthy, I suggest you get a geek in. I'll collect my Epic on Sunday thanks.
    Rik - Thursday, 20 September, 2007 11:10
  • I'm so pissed I didn't get to go flying :( Next time. Oh - this is an awesome shot!
    Darren Wood - Thursday, 20 September, 2007 16:55
  • hey, wild guess here you never know you may have gone over the limit (internet download wise) and you may have been "punished" back down to dial up speed. this wouldn't affect your lan ( your pc and server) but anything outside this would be affected whether uploading or downloading. in which case you would have to wait till your isp takes your limiter off, or contact your isp and explain your situation. as i say.. just a guess as i recently had some problems of this sort. Hope it helps
    Aidan - Friday, 21 September, 2007 9:15
  • Alright, I'll take a crack. I assume you're trying to access your server with www.spudooli.com. Create an entry in your windows hosts file which points www.spudooli.com to the internal IP address of your server. Once you've made the change, completely quit your browser, reopen and try browsing to www.spudooli.com. cheers
    Steve Baker - Friday, 21 November, 2008 14:38

All commments are held for moderated before publication so your words will not appear until we are ready.