|
| |
Just because you can ping the port on your webserver, it is not always true
that you can access the port on your webserver.
So, we want to setup a server on a windows platform, and everything works
from the local port. But, it will not work from any IP address that you can
think of. Except from the server on the server's IP
address?
After going through the sage of the Network
Firewall, I truly thought that I was on my way.
Oh contrai moni me (someone tell me how to spell this, it has been a few
years since I was working in France)
I could access the server from the server, but not from anywhere else. I
thought I had a bad install of the Sun Java Application Server, so I decided to
simplify things. And, besides, I was getting really good at installing and
setting up the apache server. Oh, the great world of java. And all this just so
that I could finally get my LDAP project working smoothly!
But, I digress.
So, I decided to install a plain old version of apache 2 to keep the possibilities
way down. And, about 15 minutes later, my generic apache server was running and
listening on ports 80 and 81. This allows me to easily check my configurations.
Anybody can get the default port working, so add a check port, so that you can
see that you are really doing something.
Again, the local would work and the local IP would work on the server, but
the client could not access the webserver. However, we did get that ping this
going, so everybody could ping everybody.
So, now I finally decided to goto the spot that I should have checked in the
first place. Error and access logs!
I cleaned up (or out) all of my error logs in XP. Even the apache logs. I
could only see the refers from the localhost and local IP, but nothing from the
client machine.
|
That was odd, so I decided to see what the network monitors would tell
me, on the server. Nothing really interesting, until I looked at the intrusion
logs for Black ICE!
There was really a lot of stuff in there, so I took the time to clean
that out as well.
And an intruder showed up!!!!!!!!

It seems that Black ICE thought that no one should be access the
webserver, especially someone trying to get webpages from the
webserver.
And even more so, especially my client PC, who was requesting pages
from the webserver. |
|
You will need to mark that IP as Trust
and Accept!

And don't forget to click the OK button!

Well, OK, the YES button.
If things worked well, then your client computer will be removed from
the intruder's list and added to your firewall buddies list.
And you will now be able to surf to your apache server's default page
and access the manual, online from the client computer.

Again, after clicking the YES button, your client PC will
be added to the acceptable characters list.

There is a panel, where you can tell who is trusted:

|
| Again, as I mentioned on other pages on my website, this
just happens to be one of the products that I am using. And, it was my
misfortune that this computer had it running. The product is great and it
does a fine job!
Eventually, I will create myself a traveling computer lab. It is really
nice ot be able to be home, and just go out to the lab and do things.
In a nice lab, you have all the protection sitting in another room. You
know firewalls and anti=virus and the other lot.
But, in your lab, you always want to have a clean
environment, so that you tools do not get in the way of
your development and prototyping.
The next time, I drive to Vegas, I hope it does not snow on the way
back :-))) |
readers if this message since I stayed up late on November 21th
2004 after driving through a snow blizzard outside of Las Vegas
California. |
|