I have filed a bug report on nic configuration problems for 10.0 and 10.1 bug #120332 in the 10.0 bugzilla. I can get a connection ,after 4-8 repeated configurations of the nic card thru yast, with every other config deleting the previous config. I can not find *anything* that the repeated configs change, that's the crazy thing about it... Of course the same setup works great when i switch to the 9.3 partition, it has also worked flawlesly for 9.1 and 9.2 when they were installed in the system. whatever was changed between 9.3 and 10.0 needs to be looked at very carefully. In the meantime 10.0 stays in the "play" partition. d. On Sunday 23 October 2005 05:10 pm, Stephen Boddy wrote:
On Monday 24 October 2005 01:12, Doug McGarrett wrote:
Please tell me what to look for. I can't send you the output of the command. Very roughly, it looks like this:
eth 0 Link encap:Ethernet HW addr 00: and more inet6 addr: fe80: and more UP BROADCAST NOTRAILERS MULTICAST MIU:5100 Metric:1 Rx packets:0 everything 0 TX packets 0 everything 0 collisisions: 0 txqueuelen: 1000 RX bytes 0 TX bytes 0 Interrupt 11
Right, this is the important bit. The lack of a line looking like:
inet addr:192.168.xxx.yyy Bcast:192.168.xxx.255 Mask:255.255.255.0
Obviously I'm removing the numbers where it's xxx.yyy, and the first two numbers may be different as well. The important bit is that they are there.
This line means that the kernel is loading the module for the NIC, but the interface is not being configured. Now I think you said that this interface is configured for DHCP in an earlier message. Double check in YaST that the NIC is configured with DHCP.
If that is the case, and the ifconfig command does not show a line like the one above, try as root:
# dhcpcd -B eth0
then check ifconfig again.
Incidentally, you do have a DHCP server in your network somewhere? Otherwise you are sending out a broadcast message and waiting for a response that never comes. How is your Windows machine configured? DHCP, or a static IP? -- Steve Boddy