Re: YaST won't work

From: Bruce Stewart (bruce_stewart_at_by.co.uk)
Date: 05/23/05

  • Next message: Bob: "Re: nvidia driver" 
    Date: Sun, 22 May 2005 23:57:39 GMT

    lakester wrote:

    > On Sat, 21 May 2005 23:46:27 +0200, *** Voorthuis <***@none.nowhere>
    > wrote:
    >
    >>lakester wrote:
    >>
    > <<Snip>>
    >>> That should do it?
    >>
    >>Doesn't matter, you could just do 'rm /etc/resolv.conf'
    > <<Snip>>
    >>The spaces are correct.
    >>*** Voorthuis
    >
    > I made the changes as root, then redid the settings in YaST.
    > Still, no go. I tried it with both Static IP Addresses and with Auto
    > Update with DHCP, and in both cases I get a 'duplicate IP addresses
    > messages'. There *was* some change, now when I start Firefox it
    > doesn't give me the 'can't find Google' message immediately. I can
    > also see my moden light flashing randomly, while Firefox sits there
    > spinning its' dotted circle.
    >
    > Thanks, lakester

    There are two issues here.
    Firstly IP connectivity, ie can you communicate to and beyond the modem.
    Secondly the name resolution, ie the convertion of urls and address names to
    IP addresses.
    We don't know if you are having a basic TCP/IP set up problem, or a problem
    with name resolution.

    Right, firstly we need to get your current setup from Windows so we are not
    chasing our tails!.
    Reboot into Windows.
    Open up a DOS prompt (Start menu/Programs/Accessories/Dos Prompt (it may be
    command prompt))
    type in: winipcfg then press return
    This should then start the program which tells you your current network
    settings in Windows. You may have to set the option to your current
    connection.
    Note down whether it is using either using DHCP or fixed. If using fixed,
    note down the IP Address, gateway, network mask and DNS server(s).
    Close the winipcfg program.
    Right now, reboot into Linux
    Show the boot process when booting into Linux by pressing F3.
    Look for the network setup, see if this is being carried out in the boot
    process.
    Log in as normal.
    Now open up YaST and set your IP address and/or DHCP settings to those in
    Windows.
    Now after this and confirmed everything in YaST.
    Open up a Konsole (the icon with a Screen with a shell infront of it)
    To confirm what your current IP Address is type in:
    /sbin/ifconfig
    Then press return, it should show something like this:

    bruce@pathfinder:~> /sbin/ifconfig
    eth0 Link encap:Ethernet HWaddr 00:01:02:2C:39:D0
              inet addr:192.168.0.32 Bcast:192.168.0.255 Mask:255.255.255.0
              inet6 addr: fe80::204:76ff:fe4c:d9d0/64 Scope:Link
              UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
              RX packets:13826 errors:0 dropped:0 overruns:0 frame:0
              TX packets:10373 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:10758176 (10.2 Mb) TX bytes:900478 (879.3 Kb)
              Interrupt:10 Base address:0xe800

    lo Link encap:Local Loopback
              inet addr:127.0.0.1 Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING MTU:16436 Metric:1
              RX packets:305 errors:0 dropped:0 overruns:0 frame:0
              TX packets:305 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:38346 (37.4 Kb) TX bytes:38346 (37.4 Kb)

    bruce@pathfinder:~>

    Checking your gateway, type in the following :
    /sbin/route
    Then press return, it should show something like this:

    bruce@pathfinder:~> /sbin/route
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
    link-local * 255.255.0.0 U 0 0 0 eth0
    loopback * 255.0.0.0 U 0 0 0 lo
    default 192.168.0.2 0.0.0.0 UG 0 0 0 eth0
    bruce@pathfinder:~>

    The gateway should be set to whatever your modem IP Address is:
    Now we need to test your basic TCP/IP connectivity, Now type in:
    ping -n 182.168.0.1
    Then press return, you should see something like this:, you will need to
    press CTRL+C to stop the updates. (My gateway is at 192.168.0.2)

    bruce@pathfinder:~> ping -n 192.168.0.2
    PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
    64 bytes from 192.168.0.2: icmp_seq=1 ttl=150 time=0.501 ms
    64 bytes from 192.168.0.2: icmp_seq=2 ttl=150 time=0.496 ms
    64 bytes from 192.168.0.2: icmp_seq=3 ttl=150 time=0.491 ms
    64 bytes from 192.168.0.2: icmp_seq=4 ttl=150 time=0.496 ms

    --- 192.168.0.2 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 2999ms
    rtt min/avg/max/mdev = 0.491/0.496/0.501/0.003 ms

    Now if you are getting connectivity here, let us try connectivity out on to
    the Internet, we'll try suse.com (195.135.220.3) , Now type in:
    ping -n 195.135.220.3
    Then press return, you should see something like this:, you will need to
    press CTRL+C to stop the updates.

    bruce@pathfinder:~> ping -n 195.135.220.3
    PING 195.135.220.3 (195.135.220.3) 56(84) bytes of data.
    64 bytes from 195.135.220.3: icmp_seq=1 ttl=52 time=59.0 ms
    64 bytes from 195.135.220.3: icmp_seq=2 ttl=52 time=86.8 ms
    64 bytes from 195.135.220.3: icmp_seq=3 ttl=52 time=57.4 ms
    64 bytes from 195.135.220.3: icmp_seq=4 ttl=52 time=46.1 ms

    --- 195.135.220.3 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3001ms
    rtt min/avg/max/mdev = 46.113/62.380/86.845/14.985 ms

    If you get destination host unreachable, it looks like you are not getting
    out to the internet.

    If you are connecting try typing in:
    dig suse.com
    Then press return, you should see something like this:

     bruce@pathfinder:~> dig suse.com

    ; <<>> DiG 9.3.1 <<>> suse.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40107
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;suse.com. IN A

    ;; ANSWER SECTION:
    suse.com. 1866 IN A 195.135.220.3

    ;; Query time: 740 msec
    ;; SERVER: 192.168.0.2#53(192.168.0.2)
    ;; WHEN: Mon May 23 00:39:02 2005
    ;; MSG SIZE rcvd: 42

    bruce@pathfinder:~>

    In the answer section you should see something similar if everything is OK.
    But again the server address will either be your modem or your ISPs DNS
    servers.

    The final test if everything so far is OK, type in :
    ping suse.com
    Then press return, you should see something like this:, you will need to
    press CTRL+C to stop the updates.

    bruce@pathfinder:~> ping suse.com
    PING suse.com (195.135.220.3) 56(84) bytes of data.
    64 bytes from turing.suse.de (195.135.220.3): icmp_seq=1 ttl=52 time=46.0 ms
    64 bytes from turing.suse.de (195.135.220.3): icmp_seq=2 ttl=52 time=95.5 ms
    64 bytes from turing.suse.de (195.135.220.3): icmp_seq=3 ttl=52 time=65.5 ms
    64 bytes from turing.suse.de (195.135.220.3): icmp_seq=4 ttl=52 time=47.7 ms

    --- suse.com ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3001ms
    rtt min/avg/max/mdev = 46.068/63.718/95.578/19.912 ms
    bruce@pathfinder:~>

    It maybe worthwhile if you are still having problems, to paste the results
    from the above commands into a text editor (Kedit for example
    (Utilities/Editors/Kedit)) and save them out to your Windows partition, so
    we can get an idea where the problem is.

    Hope this helps.

    Bruce S. 

    -- 
Replace the by by blueyonder.
  • Next message: Bob: "Re: nvidia driver"