Thanks for all the help.
Everything is working now. I still don't know the
exact cause of the problem . I was playing with it last
night, got angry and rebooted the server. After that
it worked. Did I mention I was running windows grin?
Nothing changed. The IP address for the server stayed
- Original Message -
From: Kenny Donahue [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: gnhlug [EMAIL PROTECTED]
Sent: Wednesday, April 03, 2002 1:31 PM
Subject: Re: Apache server attbi question: Update
Thanks for all the help.
Everything is working now.
A.
I still don't know
If you are inside your network, and you are pointing the browser at the
external ip address, you may need to go through an external proxy to
properly route the traffic out then back in. It is possible that ATT is
blocking incomming http, but that is doubtful. You could give us the IP
address, and
In a message dated: Tue, 02 Apr 2002 10:11:44 EST
Kenny Donahue said:
Hi all,
This is a little bit off topic but has anyone
been able to get their Apache server working
with the change from Mediaone.net to attbi.com?
I am really stuck. I changed my dyndns.org info
to show ne.client2.attbi.com
mike ledoux wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Apr 02, 2002 at 10:11:44AM -0500, Kenny Donahue wrote:
This is a little bit off topic but has anyone
been able to get their Apache server working
with the change from Mediaone.net to attbi.com?
Mine's working
On Tue, 2 Apr 2002 [EMAIL PROTECTED] wrote:
Of course, this doesn't show that they're filtering http, howerver,
be forewarned, from what I hear, running a server at your end of an
attbi connection *is* a violation of your service agreement, contrary
to the way things were under M1.
It is,
In a message dated: Tue, 02 Apr 2002 10:25:51 EST
mike ledoux said:
mwl@voyager:~host ne.client2.attbi.com
mwl@voyager:~
I suspect you're missing something fairly important there, like your
actual hostname. I also use dyndns.org, but I just point my dyndns
names directly at my IP, and
Just as a datapoint, I've had my Apache Server accessible via my
attbi account for a few months now. Seems to work OK. (eg. Nimbda
seems to have no problem hitting the server, 10-20 times a day, and
trying to infect me :-) )
The way it's setup is, Apache is on my linux box, which is on my
- Original Message -
From: Kenneth E. Lussier [EMAIL PROTECTED]
To: Kenny Donahue [EMAIL PROTECTED]
Cc: gnhlug [EMAIL PROTECTED]
Sent: Tuesday, April 02, 2002 3:20 PM
Subject: Re: Apache server attbi question
If you are inside your network, and you are pointing the browser
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Rich C hath spake thusly:
I have found this to be the case with my setup, but I thought it was
due to my SMC router. When I set up a virtual host in the router to
route http port 80 to my internal machine (192.168.1.x)
On Tue, 2002-04-02 at 12:06, Derek D. Martin wrote:
If you want to test it from inside your network, you can use an open
proxy on someone else's network. If you don't know of any (I don't),
then try surfing to it with anonymizer.com. I can't test it easily
here, but I believe that will
At 12:06 PM -0500 4/2/02, Derek D. Martin wrote:
...When I set up a virtual host in the router to
route http port 80 to my internal machine (192.168.1.x) port 80, the web
site is NOT visible from inside the network, but it IS visible to people
outside.
I believe what causes this is that
On Tue, 2 Apr 2002, Derek D. Martin wrote:
I believe what causes this is that the router forwards the source IP
and port (that of the client) to the virtual host as-is (i.e. it does
not NAT the client). Since the IP address is internal, the server
sends the traffic to it directly, rather
On Tue, 2 Apr 2002, Jack Hodgson wrote:
From inside my local net I could only http, telnet, ftp, etc. to the
linux box (also inside my local net) via the local net ip num.
But then I updated the firmware in my linksys router, and now I can
use the external domain name, and/or ip num, and
- Original Message -
From: Derek D. Martin [EMAIL PROTECTED]
To: GNHLUG [EMAIL PROTECTED]
Sent: Tuesday, April 02, 2002 5:06 PM
Subject: Re: Apache server attbi question
I believe what causes this is that the router forwards the source IP
and port (that of the client) to the virtual
- Original Message -
From: Derek D. Martin [EMAIL PROTECTED]
To: GNHLUG [EMAIL PROTECTED]
Sent: Tuesday, April 02, 2002 5:06 PM
Subject: Re: Apache server attbi question
I believe what causes this is that the router forwards the source IP
and port (that of the client) to the virtual
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Rich C hath spake thusly:
not NAT the client). Since the IP address is internal, the server
sends the traffic to it directly, rather than back through the router.
The client is expecting a reply from www.myhost.com, but
On Tue, 2 Apr 2002, Rich C wrote:
I have found this to be the case with my setup, but I thought it was
due to my SMC router. When I set up a virtual host in the router to
route http port 80 to my internal machine (192.168.1.x) port 80, the web
site is NOT visible from inside the network,
On Tue, 2002-04-02 at 15:21, Bill Mullen wrote:
Local
connections to Apache are now only possible by giving the internal IP of
the server box; the old URL still works fine from the outside world - and
yes, he's on attbi. :)
This has nothing to do with ATT (for once). It's just the nature of
On Tue, 2 Apr 2002, Kenny Donahue wrote:
I am really stuck. I changed my dyndns.org info
to show ne.client2.attbi.com but I still get nothing.
I tried changing apache to use port 91(random number)
instead of 8080 in case attbi was blocking 8080.
I tried using the IP address of my Linksys
20 matches
Mail list logo
