Okay, I'm at the end of my proverbial rope.
I've got a Windows XP Pro box running Apache 1.3.27.
I use Argosoft for my mail client, and I've changed the configuration
of it so that I can access the web-based client on port 443 (getting
around funky work firewall issues).
This setup worked just fine while I was hooked directly to the cable
connection. I could download files from my webserver without issue.
Over the weekend I added a Linksys NR041 DSL/Cable router, as well as
another computer...then the fun started.
I manually assigned IP addresses for both computers on a non-routable
IP address that is NOT the "normal" 192.168.x.x network that Microsoft
defaults to. Both computers can talk to each other and they both have
internet access.
That's where the good news ends.
I can access the website from the Pro box, but the other (Windows XP
Home) can't. Some people outside of the network can access the page,
some can't...including me while I'm at work.
I've been trying all day to get in because I KNOW I can...I was able
to get in on my first try this morning, but subsequent tries failed.
When I WAS able to get in, I started downloading files...all of the
files downloaded except one...which stopped about 1/2 way through.
When I tried to refresh the page the file was downloaded from, I
couldn't connect again.
I tried flushing out my dnscache, no help.
Eventually, I COULD connect, and I was able to download the file
again.
Now I can't seem to connect once again.
GAH.
The ONLY thing that was changed was that I added the Linksys router
and specified the IP address for my box. The box is in the router's
DMZ, but the connection is flakey. I've also set the router to
forward the port 80 communications to my box (as well as 443, 21, 25,
110, etc), even though it's probably redundant given that it's in the
DMZ.
The ODD part of all of this (and what leads me to believe it might be
an issue with the Apache configuration) is that I can access and use
my mail server's web client all day long without any problems...this
tells me that ports 443, 110 and 25 are all available and
working...it's just the web server that's having such problems.
The error and access logs don't show anything useful, just the normal
script kiddie hits.
Anyone have any ideas what I should check? Help, please! I'm begging
you!
FAQ
Profile
Private Messages
Log in
