Re: Apache on XP Pro SP2 - who blocks my port 80

From: TheJetPilot (roberto_at_skynet.it)
Date: 03/22/05

  • Next message: pcunix: "Re: Dedicated vs. shared hosting?"
    Date: 22 Mar 2005 00:49:43 -0800
    
    

    "The Q" <theqmaster@gmail.com> wrote in message news:<1110487304.735289.190410@l41g2000cwc.googlegroups.com>...
    > Hi,
    >
    > I'm having some issues with an apache 2.0.xx server running on a XP Pro
    > SP2 machine.
    >
    > My network
    > Cable modem->router(linksys)->desktop(wired) ( open ports 80, 8080 )
    > ->laptop(wireless) ( open port 8080 )
    >
    > The apache2 in install and running proper on my desktop at port 80 in
    > my LAN.
    >
    > The laptop is visible from outside of the router( internet ) when
    > people try to connect to it.
    > It's a different story from the laptop none of the two are available.
    >
    > I did disable all the firewall software ( MCAffe that took over the
    > microsoft firewall )
    > Actually I have McAffe firewall on the laptop as well, both machines
    > have fixed IP addresses in the LAN, I could not see difference in the
    > TCP/IP settings.
    >
    > Any idea what can be wrong or direction I have to reseach ?
    >
    > I was planning to install the apache2 on the laptop to see if is
    > working but I don't yet see why wouldn't work.
    >
    >
    > Finally I've managed to open 8081 on my desktop and now I see also the
    > 8080 but the 80 is seams to be blocked by someone
    > - ISP( comcast ) - anyone knows anything about that ?
    > - firewall (?) - I have mcaffe but I'd exited while testing
    > - antispyware( microsoft, spysweep ) - I'm uninstalled microsoft-as
    > still nothing
    > - the windows firewall ( it's disabled )
    >
    > I had installed before MS IIS but I've stopped, anyhow the
    > http://localhost/ is alive and kicking.
    >
    > I don't see why anyone (software) would block that port number without
    > letting me know.
    >
    >
    > I hope it's not my ISP...Anyone knows, does Comcast bloc 80, their
    > answer is pending...Is there a way to find how blocs port 80 ?
    >
    > The Q

    Hi, I don't know if you've solved your problem yet. Anyway, I had a
    similar problem tomorrow and, after inspecting my network's
    connections with the "netstat -an" dos command, I noticed that a
    program was blocking the port 80 (I got something like TCPIP
    0.0.0.0:80 LISTENING).
    The program blocking that port was SKYPE. If it's your case, look at
    the configuration window of SKYPE: you'll find that under the
    connection tab there's a checkbox that allows skype to listen to port
    80 as an alternative. If you uncheck it, you can allow apache2 to
    start correctly.
    Hope this may help you.
    bye


  • Next message: pcunix: "Re: Dedicated vs. shared hosting?"

    Relevant Pages

    • Re: Why unidirectional ping in LAN?
      ... >>>I'm imagining the ping from the laptop hits R2 who notices the destination ... so he repeats that packet on all his LAN ... >> assuming that you've connected the WAN port of R2 to a LAN ...
      (microsoft.public.windowsxp.network_web)
    • Re: Why unidirectional ping in LAN?
      ... I ping 192.168.3.11 and I get "Request Timed Out". ... >From the laptop, I ping 192.168.3.160 and it's fine. ... >>> assuming that you've connected the WAN port of R2 to a LAN ...
      (microsoft.public.windowsxp.network_web)
    • Re: Why unidirectional ping in LAN?
      ... >The problem I'm trying to figure out, is why the laptop can ping the desktop but not vice-versa. ... assuming that you've connected the WAN port of R2 to a LAN ...
      (microsoft.public.windowsxp.network_web)
    • Opening listening sockets
      ... I have a program that opens a listening socket on a LAN PC - it listens for a ... followed by the port number. ... My router, is a laptop connected directly to the internet, when I run my ... my LAN PC, he can not connect. ...
      (microsoft.public.win32.programmer.networks)
    • [SLE] Apache2 and SSL
      ... Apache runs fine on http, but https on port 443 is a problem. ... I went to yast>network services>http server configuration, and added listen to port 443. ... Deleting listen on port 443 produces a running apache2 again, but still not on ssl. ...
      (SuSE)