Just installed apache, cant connect from home LAN
Just installed apache, cant connect from home LAN
am 12.05.2007 21:26:21 von GS
I installed the latest apache and php so I could test web pages that I
use some server side php code with. It works fine when I type in
http://localhost/mypage or http://pcname/mypage from the machine I have
it installed on, but when trying to connect from another pc on my home
network that still has IE6 on it I cant get it to serve up the page.
I've tried the http://pcname/mypage, http:///mypage, as well
as http://pcname:80/mypage with no success.
What am I missing here?
thanks in advance
Re: Just installed apache, cant connect from home LAN
am 12.05.2007 21:49:36 von unknown
Post removed (X-No-Archive: yes)
Re: Just installed apache, cant connect from home LAN
am 13.05.2007 05:41:24 von GS
Davide Bianchi wrote:
> On 2007-05-12, GS wrote:
>> What am I missing here?
>
> Maybe you have a firewall that prevent connections or you are
> missing a DNS that can resolve the name of the machine. What happen
> if you use the ip address of the machine instead of his name?
>
> Davide
>
Same thing, I can ping the web hosting machine fine, using dns name or
ip address. I have all local firewalls disabled, the only firewall in
place is on my router.
Re: Just installed apache, cant connect from home LAN
am 13.05.2007 14:19:46 von shimmyshack
On May 13, 4:41 am, GS wrote:
> Davide Bianchi wrote:
> > On 2007-05-12, GS wrote:
> >> What am I missing here?
>
> > Maybe you have a firewall that prevent connections or you are
> > missing a DNS that can resolve the name of the machine. What happen
> > if you use the ip address of the machine instead of his name?
>
> > Davide
>
> Same thing, I can ping the web hosting machine fine, using dns name or
> ip address. I have all local firewalls disabled, the only firewall in
> place is on my router.
are you using named virtual hosts?
what ip is apache listening on?
goto a command prompt and run
netstat -aonb
you should see something like this:
TCP 10.10.10.10:443 0.0.0.0:0 LISTENING
900
[apache.exe]
and elsewhere this
TCP 10.10.10.10:80 0.0.0.0:0 LISTENING
900
[apache.exe]
or 0.0.0.0 on port 443 and 80
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 900
[apache.exe]
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 900
[apache.exe]
however the IP might be 127.0.0.1
TCP 127.0.0.1:443 0.0.0.0:0 LISTENING 900
[apache.exe]
TCP 127.0.0.1:80 0.0.0.0:0 LISTENING 900
[apache.exe]
if it is 127.0.0.1 then you wont be able to access it from another
machine because it is not listening on the IP assocaited with the
Network card.
to make sure apache is actually listening on all IP address, simply
remove from the httpd.conf any IP from the Listen or bind directive.
Listen *.80 will cause it to listen all IPs on port 80.
while in the command prompt what to you get when you do
telnet serverIP 80
GET / HTTP/1.1[enter][enter]
you might not see the GET ... line
what do you get when you run the exact command on the actual server?
Re: Just installed apache, cant connect from home LAN
am 13.05.2007 14:21:04 von shimmyshack
On May 13, 4:41 am, GS wrote:
> Davide Bianchi wrote:
> > On 2007-05-12, GS wrote:
> >> What am I missing here?
>
> > Maybe you have a firewall that prevent connections or you are
> > missing a DNS that can resolve the name of the machine. What happen
> > if you use the ip address of the machine instead of his name?
>
> > Davide
>
> Same thing, I can ping the web hosting machine fine, using dns name or
> ip address. I have all local firewalls disabled, the only firewall in
> place is on my router.
oh and by the way pinging just shows that your network allows pinging,
it doesnt use the same port as apache so doesnt gaurantee things will
work, do you have the XPSP2 firewall up as well, right click the
network connection and stop it, or goto services.msc and stop the
windows internet connection sharing and firewall service.
Re: Just installed apache, cant connect from home LAN
am 19.05.2007 20:50:40 von GS
shimmyshack wrote:
> On May 13, 4:41 am, GS wrote:
>> Davide Bianchi wrote:
>>> On 2007-05-12, GS wrote:
>>>> What am I missing here?
>>> Maybe you have a firewall that prevent connections or you are
>>> missing a DNS that can resolve the name of the machine. What happen
>>> if you use the ip address of the machine instead of his name?
>>> Davide
>> Same thing, I can ping the web hosting machine fine, using dns name or
>> ip address. I have all local firewalls disabled, the only firewall in
>> place is on my router.
>
> are you using named virtual hosts?
> what ip is apache listening on?
> goto a command prompt and run
> netstat -aonb
> you should see something like this:
> TCP 10.10.10.10:443 0.0.0.0:0 LISTENING
> 900
> [apache.exe]
>
> and elsewhere this
>
> TCP 10.10.10.10:80 0.0.0.0:0 LISTENING
> 900
> [apache.exe]
>
> or 0.0.0.0 on port 443 and 80
>
> TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 900
> [apache.exe]
> TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 900
> [apache.exe]
>
> however the IP might be 127.0.0.1
> TCP 127.0.0.1:443 0.0.0.0:0 LISTENING 900
> [apache.exe]
> TCP 127.0.0.1:80 0.0.0.0:0 LISTENING 900
> [apache.exe]
>
> if it is 127.0.0.1 then you wont be able to access it from another
> machine because it is not listening on the IP assocaited with the
> Network card.
>
> to make sure apache is actually listening on all IP address, simply
> remove from the httpd.conf any IP from the Listen or bind directive.
> Listen *.80 will cause it to listen all IPs on port 80.
>
> while in the command prompt what to you get when you do
> telnet serverIP 80
> GET / HTTP/1.1[enter][enter]
>
> you might not see the GET ... line
>
> what do you get when you run the exact command on the actual server?
Thanks - here is the what shows up when I enter netstat -aonb for a few
seconds:
Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 1184
[httpd.exe]
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 1816
c:\windows\system32\WS2_32.dll
C:\WINDOWS\system32\RPCRT4.dll
c:\windows\system32\rpcss.dll
C:\WINDOWS\system32\svchost.exe
-- unknown component(s) --
[svchost.exe]
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
[System]
TCP 127.0.0.1:1025 0.0.0.0:0 LISTENING 3840
[alg.exe]
TCP 127.0.0.1:4664 0.0.0.0:0 LISTENING 4408
[GoogleDesktopIndex.exe]
TCP 127.0.0.1:6999 0.0.0.0:0 LISTENING 3304
[tmproxy.exe]
TCP 127.0.0.1:40000 0.0.0.0:0 LISTENING 660
[TmPfw.exe]
TCP 192.168.1.102:139 0.0.0.0:0 LISTENING 4
[System]
TCP 127.0.0.1:1027 127.0.0.1:40000 ESTABLISHED 736
[PcCtlCom.exe]
TCP 127.0.0.1:1283 127.0.0.1:1284 ESTABLISHED 4496
[THUNDE~1.EXE]
TCP 127.0.0.1:1284 127.0.0.1:1283 ESTABLISHED 4496
[THUNDE~1.EXE]
TCP 127.0.0.1:1851 127.0.0.1:1852 ESTABLISHED 4148
[FIREFOX.EXE]
TCP 127.0.0.1:1852 127.0.0.1:1851 ESTABLISHED 4148
[FIREFOX.EXE]
TCP 127.0.0.1:3178 127.0.0.1:6999 ESTABLISHED 4148
[FIREFOX.EXE]
TCP 127.0.0.1:3253 127.0.0.1:6999 ESTABLISHED 4148
[FIREFOX.EXE]
TCP 127.0.0.1:6999 127.0.0.1:3178 ESTABLISHED 3304
[tmproxy.exe]
TCP 127.0.0.1:6999 127.0.0.1:3253 ESTABLISHED 3304
[tmproxy.exe]
TCP 127.0.0.1:40000 127.0.0.1:1027 ESTABLISHED 660
[TmPfw.exe]
TCP 192.168.1.102:2463 207.46.111.84:1863 ESTABLISHED 5680
[MsnMsgr.Exe]
TCP 192.168.1.102:3179 209.85.139.18:80 ESTABLISHED 3304
[tmproxy.exe]
TCP 192.168.1.102:3220 72.246.51.22:80 ESTABLISHED 5680
[MsnMsgr.Exe]
TCP 192.168.1.102:3254 209.85.139.18:80 ESTABLISHED 3304
[tmproxy.exe]
TCP 192.168.1.102:3276 199.185.223.78:119 ESTABLISHED 4496
[THUNDE~1.EXE]
TCP 192.168.1.102:2885 142.177.145.149:80 CLOSE_WAIT 4408
[GoogleDesktopIndex.exe]
TCP 127.0.0.1:3138 127.0.0.1:6999 TIME_WAIT 0
TCP 127.0.0.1:6999 127.0.0.1:3192 TIME_WAIT 0
TCP 127.0.0.1:6999 127.0.0.1:3208 TIME_WAIT 0
TCP 192.168.1.102:3139 72.246.51.8:80 TIME_WAIT 0
TCP 192.168.1.102:3272 72.246.51.106:80 TIME_WAIT 0
UDP 0.0.0.0:40116 *:* 736
[PcCtlCom.exe]
UDP 0.0.0.0:500 *:* 1456
[lsass.exe]
UDP 0.0.0.0:4318 *:* 384
C:\WINDOWS\system32\mswsock.dll
c:\windows\system32\WS2_32.dll
c:\windows\system32\DNSAPI.dll
c:\windows\system32\dnsrslvr.dll
C:\WINDOWS\system32\RPCRT4.dll
[svchost.exe]
UDP 0.0.0.0:4319 *:* 384
C:\WINDOWS\system32\mswsock.dll
c:\windows\system32\WS2_32.dll
c:\windows\system32\DNSAPI.dll
c:\windows\system32\dnsrslvr.dll
C:\WINDOWS\system32\RPCRT4.dll
[svchost.exe]
UDP 0.0.0.0:1028 *:* 384
C:\WINDOWS\system32\mswsock.dll
c:\windows\system32\WS2_32.dll
c:\windows\system32\DNSAPI.dll
c:\windows\system32\dnsrslvr.dll
C:\WINDOWS\system32\RPCRT4.dll
[svchost.exe]
UDP 0.0.0.0:1121 *:* 384
C:\WINDOWS\system32\mswsock.dll
c:\windows\system32\WS2_32.dll
c:\windows\system32\DNSAPI.dll
c:\windows\system32\dnsrslvr.dll
C:\WINDOWS\system32\RPCRT4.dll
[svchost.exe]
UDP 0.0.0.0:1792 *:* 384
C:\WINDOWS\system32\mswsock.dll
c:\windows\system32\WS2_32.dll
c:\windows\system32\DNSAPI.dll
c:\windows\system32\dnsrslvr.dll
C:\WINDOWS\system32\RPCRT4.dll
[svchost.exe]
UDP 0.0.0.0:4320 *:* 384
C:\WINDOWS\system32\mswsock.dll
c:\windows\system32\WS2_32.dll
c:\windows\system32\DNSAPI.dll
c:\windows\system32\dnsrslvr.dll
C:\WINDOWS\system32\RPCRT4.dll
[svchost.exe]
UDP 0.0.0.0:4500 *:* 1456
[lsass.exe]
UDP 0.0.0.0:445 *:* 4
[System]
UDP 0.0.0.0:4321 *:* 384
C:\WINDOWS\system32\mswsock.dll
c:\windows\system32\WS2_32.dll
c:\windows\system32\DNSAPI.dll
c:\windows\system32\dnsrslvr.dll
C:\WINDOWS\system32\RPCRT4.dll
[svchost.exe]
UDP 0.0.0.0:2929 *:* 384
C:\WINDOWS\system32\mswsock.dll
c:\windows\system32\WS2_32.dll
c:\windows\system32\DNSAPI.dll
c:\windows\system32\dnsrslvr.dll
C:\WINDOWS\system32\RPCRT4.dll
[svchost.exe]
UDP 127.0.0.1:1405 *:* 5680
[MsnMsgr.Exe]
UDP 127.0.0.1:1900 *:* 680
^C