>Strange stuff ...
>My IPCop is configured with three adapters :
>Green : 192.168.100.1
>Orange : 192.168.200.1
>Red : DHCP from my ISP
>I have a webserver on my orange segment (cross cable) and this webserver has
>an IP : 192.168.200.50 and a gateway 192.168.200.1
>I adapt my IPCop server :
>Port forwarding : TCP 80 to 192.168.200.50:80
>External service access: tcp all 80 enable.
>My internal servers (green segment) are configured using DHCP provided by
>IPCop and receive a valid address/gateway. Gateway 192.168.100.1
>Now the problem : when I try to connect to my orange server from my green
>server, it takes a long time. Using the no-ip service doesn't work, I need
>to use the IP address (192.168.200.50) and even like that it takes time. I
>add a line in the host file of my W2K workstation and I get the initial page
>of my website but any further request doesn't work.
Sounds like DNS/route is screwy somehow...
If your web-server is set to force the URL/location to convert to the
domain-name, then the links you click on aren't using the IP -- They
are using the broken DNS hostname stuff. Look at the bottom of your
browser as you mouse over a link, and you'll see what it is going to.
IP, or domain name?
Actually -- if the IP addresses are slow, either the route is
*really* screwy, or you have a bad NIC.
What is the output from IPCop's:
And what is the output from the web-servers:
Or whatever it is under Windows... "ipconfig/a" ???
Finally, do that for the W2K box you're surfing from as well.
Look for the "Collision" numbers and compare the Tx (transmit) to Rx
Tx = Rx + Collision
If Collision is "high", then either you have broken hardware, or
their settings for TTL are bad, I think.
Disclaimer: I only half-understand this crap, at best.
Got Music? http://l-i-e.com/artists.htm