Re: absurdly simple LAN problem - SOLVED?

From: Anthony Campbell (ac_at_acampbell.org.uk)
Date: 09/19/05

  • Next message: Ron Peterson: "Re: runlevel policy"
    Date: Mon, 19 Sep 2005 15:43:40 +0100
    To: debian-user@lists.debian.org
    
    

    On 19 Sep 2005, Jared Hall wrote:
    > Anthony
    >
    > >1. There is a page in the router set-up which shows attached devices;
    > >the laptop appears here as 192.168.0.3, for some reason.
    >
    > >From what I have gathered you haven't been able to get your laptop
    > (wireless) to connect to your desktop (Ethernet). You are connecting
    > both of these machines to a router which also broadcasts a wireless
    > signal.
    > I need you to answer a couple of questions for me so we can isolate
    > the source of this problem that you have been having.
    > what is the IP address of the laptop right now? <192.168.0.3?>
    > what is the IP address of the desktop right now? <192.168.0.2?>
    > Can you get into the router and assign a static IP addresses to your
    > Desktop? <If you can this will make your networking problem a whole
    > lot more simple. this usually requires that you know your mac address.
    > use the comand <i>ifconfig</i> [eth0] on the desktops terminal to
    > find that out. It usually looks something like: "HWaddr
    > 00:A1:CD:3G:F5:Ca">.
    >

    I've added static addresses to be double-safe; things are working
    now - ssh is up and running so I'm pretty confident that is not a
    problem.

    > >2. I removed (instead of just stopping) shorewall and also bastille on
    > >both machines.
    > This seems wrong to me. You got rid of firewalls in order to network
    > your machines? If that worked for you then you just need to change
    > your firewall rules so that you LAN IP addresses will pass. I love
    > Bastille, but I don't use its firewall. have you thought of using
    > <b>iptables</b> instead? It really doesn't take much to learn how to
    > make yourself a nice software firewall.
    >
    > Anthony, please describe, in detail, your network setup. from what I
    > have gathered it looks like:
    >
    > Internet ------->Modem-------->router----------->Desktop
    > |
    > [Wireless signal
    > from router]
    > |
    > Laptop
    >
    > Jared

    Yes, this is the arrangment. I've tried reinstalling shorewall, with the
    appropriate files for a local network, but so far it keeps breaking
    things. That is, after starting it I can no longer ping to the machine
    concerned from the other; stopping shorewall is not sufficient to get
    things going and indeed even removing it doesn't help unless I reboot.
    Not sure what the problem is here; I've always got on well with
    shorewall in the past. It may just require more RTFM

    I note your suggestion about iptables but I admit I've avoided getting
    directly involved with this in the past! Cowardly, no doubt...

    Anthony

    -- 
    ac@acampbell.org.uk    ||  http://www.acampbell.org.uk for
    using Linux GNU/Debian ||  blog, book reviews, electronic  
    Microsoft-free zone    ||  books and skeptical articles
    -- 
    To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    

  • Next message: Ron Peterson: "Re: runlevel policy"

    Relevant Pages

    • Re: Norton 2005 Int Security, Trend PCcillin or Zone Alarm ???????
      ... > I want security I can run on both machines. ... System overhead is higher than standard firewall applications. ... Symantec products do not remove (uninstall) well. ... Micro Trends PC-Cillan is very good (possibly the best in home network ...
      (alt.computer.security)
    • Re: Home Network - problem adding PC to Workgroup
      ... But I CAN't seem to get it recognized by or get it to recognize the other pcs in the workgroup. ... start by running the Network Setup Wizard on all machines. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
      (microsoft.public.windowsxp.network_web)
    • Re: Sharing a printer
      ... It may look daunting, but if you follow the steps at the links and suggestions below systematically and calmly, you will have no difficulty in setting up your sharing. ... start by running the Network Setup Wizard on all machines. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
      (microsoft.public.windowsxp.network_web)
    • Re: Setting Up A WorkGroup for file and Share Printing
      ... start by running the Network Setup Wizard on all machines. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
      (microsoft.public.windowsxp.network_web)
    • Re: Setting Up A WorkGroup for file and Share Printing
      ... Tried that amd could access only one of the two drives, the D drive, however ... I Turned off NIS 2008 firewall ... I made sure the Registry setting "IRPStackSize" on both machines ... Here are general network troubleshooting steps. ...
      (microsoft.public.windowsxp.network_web)