DHCP Client Problem with Suse 20 Pro

Hello everyone, I am not new to Linux distributions and Suse 10 is a very
good one.

Nevertheless I have a small problem. I have a Suse 10 machine with 1 NIC
connected to a Cisco 1700 router. The router is enabled as a DHCP
server.If I connect a Windows machine to the Router, I get an IP and
immediatelly I have an Internet connection. But when I connect my Suse 10
machine, I get no IP address.

I tried everything, even giving a static IP but nothing happened. Then I
decided to run a Knoppix Live CD on the Suse machine and I got an IP
address immediatelly. Since there seems to be nothing wrong with the
Router, does anyone have a solution.

Thanks...

ppppapad@yahoo.com adjusted his/her tinfoil beanie to post:

> Hello everyone, I am not new to Linux distributions and Suse 10 is a
> very good one.
>
> Nevertheless I have a small problem. I have a Suse 10 machine with 1
> NIC connected to a Cisco 1700 router. The router is enabled as a DHCP
> server.If I connect a Windows machine to the Router, I get an IP and
> immediatelly I have an Internet connection. But when I connect my Suse
> 10 machine, I get no IP address.
>
> I tried everything, even giving a static IP but nothing happened. Then
> I decided to run a Knoppix Live CD on the Suse machine and I got an IP
> address immediatelly. Since there seems to be nothing wrong with the
> Router, does anyone have a solution.
>
> Thanks...

Have you entered the ip address of your router as one the DNS servers in
the config in Yast?

Or enter a couple from your ISP and have the router as a third fallback.

HTH
--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

ppppapad@yahoo.com wrote:

> Hello everyone, I am not new to Linux distributions and Suse 10 is a very
> good one.
>
> Nevertheless I have a small problem. I have a Suse 10 machine with 1 NIC
> connected to a Cisco 1700 router. The router is enabled as a DHCP
> server.If I connect a Windows machine to the Router, I get an IP and
> immediatelly I have an Internet connection. But when I connect my Suse 10
> machine, I get no IP address.

Just to be sure:
As root give the following commands in a console and report the output:
ifdown eth0
ifup eth0 -o debug
ifconfig eth0

--
Freek

I get this:

ifup [DEBUG] HWDESC = eth0
CONFIG = eth-id-00:40:95:30:70:34
INTERFACE = eth0
ifup eth0 device: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
ifup eth0 configuration: eth-id-00:40:95:30:70:34
ifup-dhcp DHCP client is already running on eth0
ifup-route [DEBUG] calling: ip route replace to default via 10.79.229.1
---> FAILED
ifup-route ERROR: Warning: Could not set up default route via
interface
Command ip route replace to default via
10.79.229.1 returned:
. RTNETLINK answers: Network is unreachable
Configuration line: default 10.79.229.1 - -
This needs NOT to be AN ERROR if you set up
multiple interfaces.
See man 5 routes how to avoid this warning.

pppapad@yahoo.com wrote:

> I get this:
>
> ifup [DEBUG] HWDESC = eth0
> CONFIG = eth-id-00:40:95:30:70:34
> INTERFACE = eth0
> ifup eth0 device: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
> ifup eth0 configuration: eth-id-00:40:95:30:70:34
> ifup-dhcp DHCP client is already running on eth0

Apparently you did not do a proper ifdown, otherwise the DHCP client would
not be running on eth0.

> ifup-route [DEBUG] calling: ip route replace to default via 10.79.229.1
> ---> FAILED
> ifup-route ERROR: Warning: Could not set up default route via
> interface
> Command ip route replace to default via
> 10.79.229.1 returned:
> . RTNETLINK answers: Network is unreachable
> Configuration line: default 10.79.229.1 - -
> This needs NOT to be AN ERROR if you set up
> multiple interfaces.
> See man 5 routes how to avoid this warning.

Go to Yast and remove all network devices. Then reconfigure your network
card. Make sure you select DHCP.

--
Freek