cannot access my sites from intranet

Looks like your computer cannot resolve url.
Can you ping that url?
...
Try to modify /etc/hosts file adding that url and its IP address and see if it helps ... short intro for editing /etc/hosts is here: http://ubuntuforums.org/showthread.php?t=3407

Good luck.

Ping was okay.

thanks,

Pinging deal66.emallguide.org [76.254.64.225] with 32 bytes of data:
Reply from 76.254.64.225: bytes=32 time=2ms TTL=255
Reply from 76.254.64.225: bytes=32 time=2ms TTL=255
Reply from 76.254.64.225: bytes=32 time=3ms TTL=255
Reply from 76.254.64.225: bytes=32 time=2ms TTL=255

Ping statistics for 76.254.64.225:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 3ms, Average = 2ms

Did you try modifying /etc/hosts ?

more /etc/hosts

127.0.0.1 localhost
127.0.1.1 XXXXXXXXXXXXXXXXXXXXXX

# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

DID NOT find any IP v4 related lines.

I think /etc/hosts.allow should be changed, but do you have an example?

thanks,

OK, so let's try this and see what happens - add to /etc/hosts below localhost line (hope IP is correct):
99.191.74.86 deal66.emallguide.org

Also, try putting to your browser request like http://99.191.74.86 it this works ...

I put
192.168.1.101 deal66.emallguide.org

and reboot the server, but still no use.
It currently has dynamic IP, so I cannot put 99.191.74.86, but internal IP is always 192.168.1.101

http://99.191.74.86 works only on different network (you can visit it from your computer of course)

thanks,

Can we summarize this for clarification?

Your target server:

Internal IP: 192.168.1.101, static
External IP: 99.191.74.86, dynamic

Your host's ip?

Location of the target server? DMZ? Directly on the Internet? Directly on the LAN?
Are the target's internal IP and external IP on separate NICs?

What is your INTERNAL domain? Let's hope it's NOT emallguide.org or you're going to have a split-horizon DNS problem.

It might sound like a dumb question, but, to cover all the bases, your local workstations CAN access the internet, right? So this problem is limited to getting to this particular host, and not a problem with getting off your LAN in general?

Can you access the server via http://192.168.1.101? Should you be able to? Remember: web servers can be told to listen on only one IP so it's possible that 192.168.1.101, while a valid address for the server, will not have a web page on it. For testing purposes, enable it if it won't conflict with something else.

Do you have access to a console on the server? What is it running, Linux, Windows?

Can the server be accessed

One important question that I'm not clear about: is ANYONE on your local network able to access this server or is it just your host?

If anyone else can, are they using Windows or Linux?

Your initial question implies that this is an internal, site-wide problem so, unless all the PC's on the LAN are running Ubuntu, I suspect this is not an issue with Ubuntu's configuration, unless they are all configured the same way.

192.168.x.x is not a (normally) routable address, so the server is going to have to be located on the same LAN as your hosts, separated only by hubs and switches. If you have to go through a router, the router, ideally should not be passing the traffic unless explicitly configured to do so, which is a bad idea. If you are passing the traffic through a router, the server should be on a DMZ. 192.168.x.x should never be passed to the internet.

Some suggested steps to test:

1) on your workstation, from a console, type:

nslookup deal66.emallguide.org

The response, when I tried it was/should be:

Server: 192.168.57.1 <-- this refers to one of my DNS servers - your's may be different.
Address: 192.168.57.1#53 <-- either way, the response here is not important

Non-authoritative answer:
Name: deal66.emallguide.org
Address: 99.191.74.86 <-- this is the answer that must match the current extenal IP of the server.

Check this address against the server's external address. They must match. If they don't, then your internal DNS source (which may or may not be what the outside world uses) has outdated DNS information. If it's outdated, you'll have to figure out why.

Repeat this step using the INTERNAL DNS name, if you have one. In this case it should resolve to 192.168.1.101

2) On the server, run Windump (for windows) or TCPdump for Linux and tell it to look for traffic from your workstation on the internal network card. I'm assuming here that you've enabled the web server on the internal interface for testing.

3) On the workstation, do the same thing:
sudo tcpdump -i eth0 -nn host 192.168.1.101 and host 192.168.1.x (your workstation IP goes here)
will display all the traffic from the server that reaches your host.

4) Ping the server's internal address from your workstation. You should see the traffic in the Windump/TCPDump output. Take note that you should see both the incoming request from your workstation AND the outgoing response.

5) On your workstation, type http://192.168.1.101. Check the server to confirm that the request arrived and confirm that the server is responding.

6) On your workstation, type http://<internal DNS name of the server> - this must be the internal name, not the external. We want to confirm that the internal DNS is working OK. The internal DNS should resolve to 192.168.1.101.

Once you've confirmed that life is good on the internal network, try to get to the external network.

7) On the server, run TCPDump/Windump using the external interface. If you're on a DMZ, the host you would be looking for is not your workstation's IP but the IP of the firewall's DMZ interface. Without a DMZ, it's the firewall's external IP that you want to be watching for. Again, looking at the server, confirm that the request came in and that a reply went back. On the workstation, run TCPdump as per step 3, but change the server's address to external address. Tell us if you see traffic both in and out on both machines.

I think we need to confirm first that traffic is flowing out of your PC in the first place, being received by the server, being answered by the server and that the answer is arriving back at your PC before looking at a problem with Ubuntu.

The hosts file is really just used (someone correct me if I'm wrong) when you need to map a host to an IP in the absence of a DNS entry.