Windows can't see Apache on Linux machine when in one location, can in other. Linux PC can see serve

Discussion in 'Linux Networking' started by Agent X, Jul 8, 2004.

  1. Agent X

    Agent X Guest

    We have two offices A and B, connected by kilostream.

    We have a Linux box in location A, running Mandrake 9 and the Apache
    web server.

    We have some Linux boxes in location B, and loads of Windows machines.

    The problem is that whenever a Windows box is in location B, it can't
    see any pages served up by the Linux based web server in A. It can
    ping it, but if you telnet to port 80 from the Windows machine you get
    nothing back.

    If I pick up the Windows machine, and transport it to location A, plug
    it into the network, all works OK.

    At the moment I'm using SQUID on a Linux box in location B as a proxy
    server for the Windows machines in location A, but this is a bodge
    really.

    Any idea why the WIndows machiens in location B can't see pages from
    the apache server in A, whilst Linux machines in B can see A ?
     
    Agent X, Jul 8, 2004
    #1
    1. Advertisements

  2. I don't know what a kilostream is so I have no clue how you are routing
    from B to A (through internet or VPN?). But Windows sometimes does some
    funky routing, so it may be a routing issue.

    Yesterday I was totally reinstalling Win98se on my boss' personal PC that
    he was giving to his daughter. And from our company LAN, I had trouble
    accessing www.adobe.com to install Acrobat reader. I noticed that adobe
    had a 192... IP, and that for some reason Win98 had a local route for
    192.0.0.0/255.0.0.0 (that explains it). I refreshed its DHCP IP and it
    ended up with corrected 255.255.255.0 for its 192.168.x.0 network, and
    then I was able to access www.adobe.com.

    So run "route print" (or is it "route /print"?) on the Win boxes to see if
    they have any strange routing or conflicts that may explain why B Win PCs
    cannot reach server on net A.
     
    David Efflandt, Jul 9, 2004
    #2
    1. Advertisements

  3. Agent X

    Yas Guest

    Hi,

    Have you tried running tcpdump on the webserver to see if connections are
    actually hitting the webserver? You mentioned it can ping but cant telnet
    to port 80. From that it sounds as if routing is working. Do you have any
    firewalls?

    Like i mentioned, i think the best place to start would be to see if
    tcpdump shows packets coming in to the webserver.

    Hope that helps
    Yas
     
    Yas, Jul 9, 2004
    #3
  4. Agent X

    Agent X Guest

    I don't think it can be routing, as you can ping OK. Also the Windows
    PC's have fixed IPs, though they do use WINS, whatever that is, and
    don't use DNS (cos our techies don't even know what DNS is.........)

    Ta, I'll check the routing. A kilostream is a 256 or 512K private
    leased line between two locations, i.e. no internet or VPN involved.
     
    Agent X, Jul 9, 2004
    #4
  5. please let us know what ip addressing scheme are you using for
    location A and B? might be the cause that iptables has been configured
    to provide access to location A.

    try running ethereal to see the diagnosis messages.

    raqueeb hassan
    congo (drc)
     
    Raqueeb Hassan, Jul 10, 2004
    #5
  6. Agent X

    Agent X Guest

    to port 80. From that it sounds as if routing is working. Do you have any
    No firewalls. To me the mystery is why can the Linux box on location B
    see everything on the Linux box in location A fine, whilst the windows
    boxes can really do nothing more than ping.
    I've had a cursory look at tcpdump but have been been blinded by the
    number of parameters on the command. What parameters do I need to pass
    to it to filter only on a particular incoming IP address, and what can
    I tell from the result sof the command ?

    Thanks for your help.
     
    Agent X, Jul 10, 2004
    #6
  7. Agent X

    Jerry Smiley Guest

    The command line string should be tcpdump host 192.xxx.xxx.xxx and
    192.xxx.xxx.xxx
     
    Jerry Smiley, Jul 10, 2004
    #7
  8. Agent X

    Agent X Guest

    please let us know what ip addressing scheme are you using for
    It can't be an iptables thing, because:

    a) its turned off
    b) if you move a laptop from location B to A it works fine.

    I'll try that too thanks.
     
    Agent X, Jul 11, 2004
    #8
  9. Agent X

    Agent X Guest

    The command line string should be tcpdump host 192.xxx.xxx.xxx and
    ta, will try that tomorrow
     
    Agent X, Jul 11, 2004
    #9
  10. Agent X

    Agent X Guest

    The command line string should be tcpdump host 192.xxx.xxx.xxx and
    OK tried that, and saw a nice lot of output when my PC telneted or
    pinged the Linux box.

    Now, bizarrely, the windows box in location B showed no output when
    either pinging (which worked) or telnetting (which worked) or
    telnetting to the apache server on port 80 (which didn't work).

    Weird.
     
    Agent X, Jul 12, 2004
    #10
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.