two questions in one

[Erik Nørgaard]

steve lasiter wrote:
> My web server is up and running well and I can test
> all by going to 192.168.0.2 from any internal
> workstation, but if I try to go to www.mywebsite.com
> from any internal workstation, which maps to the
> 66.190.xxx.xxx IP directed to web server port 80 as it
> should, my attempt will time out. If I run next door
> to my buddies and hit it from his PC I get there just
> fine. I can't understand this since I'm using the
> www.mywebsite.com name instead of an IP address. It
> seems the gateway should not be affecting me, right?
> How do I get around this or solve it? I don't want to
> have to go next door everytime I need to make sure my
> site is accessible from the web.

Sounds like a DNS lookup problem, check /etc/hosts and /etc/resolv.conf 
on the different hosts and try to do host lookup on the different hosts.

If you get different ip then there you have it.

> One other quick issue. When FTPing from within my LAN
> it is horribly slow. It was fast after initial install
> but something happened without my intervention. I've
> tried two different servers, proftpd currently and
> pureftp previously. If I ftp outside my LAN it's
> lightning fast. Any ideas are appreciated.

You are ftp'ing LAN-Internet right? Are you sure that some other user is 
not sucking up your connection with p2p? On the gateway you can see 
which states are in the firewall, assuming you have a statefull firewall 
ruleset. Ntop on the gateway should be a great tool also.

Also, ftp and firewalls generally is troublesome, maybe you changed a 
rule in the firewall just a littlebit?

Cheers, Erik

-- 
Ph: +34.666334818                           web: http://www.locolomo.org
S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt
Subject ID:  A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9
Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2