This is a discussion on Need help keeping Apache awake on RedHat 9 within the Apache Web Server forums, part of the Web Server and Related Forums category; I am not sure what my problem is or if it really is an Apache problem at all. Here are ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
I am not sure what my problem is or if it really is an Apache problem at
all. Here are the symptoms for your consideration and comment... 1. Apache 2.0 standard install (did not change any defaults) using the RedHat 9 ISOs. 2. Win2K client using IE 5.5 3. Use Mozilla from server to view home page... works fine 3. Point client to server... on LAN using IP addressing (http://192.168.x.x)... no joy 4. Ping from client to server... works fine 5. Point client to server... on LAN using IP addressing (http://192.168.x.x)... no joy 6. Ping from server to client... works fine 7. Point client to server... on LAN using IP addressing (http://192.168.x.x)... works fine 8. a few minutes pass and I try to Point client to server... on LAN using IP addressing (http://192.168.x.x)... no joy again. 9. Repeat steps 6-8 works every time. Any ideas? BTW, I am using a Linksys BEFSR41 and an Avaya AP500 wireless bridge with 802.11b wireless NIC in the client PC. Internet connectivity from both client and server works consistently all the time... no problems at all... can browse to Internet sites without any problems. It just seems to be in getting Apache to serve up pages to the client connected via the wireless bridge and the router. I have not had a chance to test whether Apache is serving up content to browser coming from the Internet yet but intend to do that as well when I can a chance. Thanks! Chip |
|
|||
|
Chip G <NOSPAMchipg_98@atyahoo.todelete.com> wrote:
> 3. Point client to server... on LAN using IP addressing > 4. Ping from client to server... works fine > 5. Point client to server... on LAN using IP addressing > 6. Ping from server to client... works fine > 7. Point client to server... on LAN using IP addressing > (http://192.168.x.x)... works fine > 8. a few minutes pass and I try to Point client to server... on LAN using IP > addressing (http://192.168.x.x)... no joy again. It looks like a cook-up in the network, I had similar problem with a busted switch. There isn't a easy way to debug that, I'll start with checking the network card an the connection between the server and the rest of the network. Davide |
| Thread Tools | |
| Display Modes | |
|
|