J. Greenlees wrote:
Brian Mearns wrote:
~snip~
Let me add another tip. Apologies if it was in the previous posts and I
missed it.
Your server is part of a local LAN, which has addresses like
192.168.2.x. Say your server is 192.168.2.100 there.
When your server gets a TCP packet containing a H
Brian Mearns wrote:
~snip~
>
> As for your problem...
A useful tool that can help diagnose the issues below is shieldsup on
grc.com
a port scan that tells you what ports ( if any ) are open. since it's
coming from outside the isp it also finds blocked ports from them.
> It's hard to say why th
On Sun, Apr 12, 2009 at 11:42 AM, E. Mail wrote:
> Hi Brian,
>
> I checked the /localhost on the server and it worked fine.
>
> I checked the server from the office machine and it worked after I set an
> HTTPD.EXE exception for the Firewall.
>
> I went to my neighbor's house and tried jrubinic.us
