On Mon, 19 Feb 2007 07:26:07 -0800 (PST)
Drew Jenkins <[EMAIL PROTECTED]> wrote:
> Yes, that is a start. I added the domain "mercury.com" (a site I never visit)
> and pointed it to 192.168.1.255, the IP address given from the above. I also
192.168.1.255 doesn't look right. in your server, run ifconfig and determine
the IP from *that* information.
For example, on my laptop:
[EMAIL PROTECTED] [Tue Feb 20 10:29:47 2007]
bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.2.129 netmask 0xffffff00 broadcast 192.168.2.255
media: Ethernet autoselect (100baseTX <full-duplex>)
the IP assigned to my network card (bge0) is 192.168.2.129 , with a netmask of
255.255.255.0 (0xffffff00 ), and a broadcast of 192.168.2.255.
The only thing you need to access your server from your workstation, if they
are in the same LAN (and subnet...;) ) is the IP address.
> updated pound to use that address, and was able to get the pound daemon
> running. However, I cannot surf to either mercury.com or the IP address. When
> I run this command: nmap localhost I discover that no Web ports are open:
> neither 80, nor 8080 (Zope), whose daemon is running. nmap 192.168.1.255
> doesn't return any ports, stating it seems the host is down. nmap
> 192.168.1.130 the other address returned from your ifconfig command, gives
> the same ports as above. Please advise.
since you are bothering with nmap...why dont you just scan all your IP space
(as in your LAN's IP subnet) and move on? :)
btw, you DO have apache running on your server, right?
It is better to remain silent and be thought a fool, than to speak, and remove
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
email@example.com mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"