Chris, Thanks a ton for the help so far! I tried your suggestions, without much luck, unfortunately. I'm thinking about just upgrading to RH 9, since I figure I should probably upgrade sometime soon anyways... However, I'm kind of curious as to what happened here... As you thought, when I ran ifconfig -a, I did not have a inet addr... So, I ran dhclient, and got the following output (i'm typing this from another screen here, so please ignore any typos)...
Listening on LPF/eth0/00:0c:6e:4a:3f:06 Sending on LPF/eth0/00:0c:6e:4a:3f:06 Listening on LPF/lo Sending on LPF/lo Sending on Socket/fallback DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 14 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 15 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21 DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 14 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 12 Does this mean anything to you??? Thanks again for all the help! ~Erin > Erin, > First off i am not too familiar with redhat, i know they have tool > > that make this stuff "easier" but since the tools they use aren't > common > to the distributions i use i don't know the "best" way to do it in > red > hat. That being said what i suggest _should_ still work. > So you lsmod and make sure that the nvnet is loaded. Then type > /sbin/ifconfig -a and make sure that there is a line that looks > like: > > eth0 Link encap:Ethernet HWaddr 0A:0A:0A:0A:0A:0A > inet addr:192.168.1.102 Bcast:192.168.0.255 > Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:107164 errors:0 dropped:0 overruns:0 frame:0 > TX packets:56200 errors:0 dropped:0 overruns:0 carrier:1 > collisions:0 txqueuelen:1000 > RX bytes:15163596 (14.4 Mb) TX bytes:8898755 (8.4 Mb) > Interrupt:11 Base address:0xec80 > > where teh HWaddr will be the mac address of your nic and the inet > addr > is your ip address. If you have something that looks just like this > with > the inet line and it looks like you have a valid ip address (if you > are > not behind a router then it should be something other than > 192.168.*.*, > i am not sure but i think most campus address are 128.*.*.* so if you > > have an inet address that looks like that and you have the UP > BROADCAST > like then your card is set up fine) > If you have a line that looks like > > eth0 Link encap:Ethernet HWaddr 0A:0A:0A:0A:0A:0A > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > Notice there is not inet addr in there, this means that your card is > set > up and being recognized fine but it has not recieved an ipaddress. So > > basically what you need to do here is tell your card to get an ip > address, and your isp should assign them through dhcp. Now this is > where > the redhat tools come in, i know the tool i use is not on redhat but > it > is something similar, i think if you type "dhcpclient eth0 " or > something like that, if you just type "dhc" and hit tab a few times > you > should see something close to what i am talking about (i know redhat > has > a graphical tool to do this but i would have to be there and look at > the > menu to figure out which one it is, it should be like a network tool > or > something) > > Now that i have said all of that since you are getting an error > "Cannot activate network device eth0" i expect that redhat is trying > to > get an address for it but for whatever reason it is failing. If > ifconfig > shows an eth0 device then i would guess it is a problem with either > the > connection (are you using a cross-over cable when you should be using > a > patch?) or your service does not want to give you an ip address (i > don't > know who you call about on campus network). > I know this may not solve your problem but it may at least help > you > narrow it down a little bit. After running ifconfig and checking that > > let us know what the status of your devices is and we'll see if we > can > figure something else out. > > -Chris ===== http://www.userfriendly.org __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
