I took the advice, and set it up. This time Yast hung trying to start network servuces. When I went to shut down and restart to test it, it hung for five minutes trying to shut down network services. I am too frustrated and will try again another day. If I don't shoot the machine. Thanks for the help! Nick On Wednesday 24 July 2002 17:09, you wrote:
go in an set the ip static to one that the dhcp server uses but high enough up in series to not be asigned by the dhcp. I do this on my main machines here at work an at home , i like to have a static ip on my windows workstation an I do the same on the linux servers I have here in the office. I asign the ip from the upper end of he series . my dhcp server here is my linksys dsl/cable router. it uses 192.168.1.? so for my work station an servers i would use 192.168.1.200 for first static ip address. i have only 25 work stations so i could start even lower.
do that an see if it will work with a static ip.
want fix the dhcp problem but it should get you up an running with a working ip address.
hth.
At 03:41 PM 7/24/2002 +0200, you wrote:
Okay. So on restart the machine recognized the card (YAY!!) but sadly couldn't get a DHCP request answered by the router. It stopped the process. It did not SKIP the process (and get the DHCP crap later) but seemed to STOP it.
When Linux started up finally, I pinged suse.com and got network is unreachable.
This is at least an improvement on "failed"
Anyone have any ideas? I write this from my notebook, connected to the same router with no difficulties whatever.
nick
On Wednesday 24 July 2002 15:33, Togan Muftuoglu wrote:
* Nick Selby;
on 24 Jul, 2002 wrote: alias eth0 nvnet
Yup-er-ooni, it's there. That mean I am cool?
Looks like but YMMV
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com