Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I had a Windows box 2 weeks ago and my connection with Comcast worked fine. Now I'm setting up my SUSE 9 on the same hardware and using DHCP from Yast (according to Comcast's technical advice), but I get no connection. SUSE recognizes and configures my Ethernet card, which is:
The motherboard is SOYO: SY-P4IS2
Everything looks perfect from Yast, but when I push Finish, I'm gettiing nothing!!
I use Comcast as well, however, I use Redhat 9.
Now I know there are differences among distro's, but I don't think this would be one.
Comcast is a very shakey service at times... For a good few months it will be absolutely rock solid, fast, and reliable.. Then occasionally for about a day or so (Once I was stuck without net access for a week) it'll just...stop.
Now, I know that sounds like a total BS answer, but it's what happened to me...
So there's crap solution number 1...
Try using your net again on a Windows box and see if it's working fine still... if so, then this may get a bit tricky.
To my knowledge, unless a internet service requires special software (AOL for example... Ew I hate them) then the internet signal should be recognized cross-platform... Now for USB use, you may have some trouble with using Comcast and Linux, as I don't know if Comcast's USB software is compatible with Linux (last time I asked, they said no.)
Now, I have that EXACT same Network card in my comp (What a coincidence) in my box... Sometimes though I need to re-enable eth0 in Redhat. I just go through the menu's of the GNOME GUI and tell it to enable whenever the cord accidently is unplugged. Might want to play around with that if you have something similar (Sorry I'm still a bit new.. Don't know the terminal command for that)
Sorry if my advice is a bit useless, but it's worth a try.
Well, I looked around and it seems there is someone else having a very similar problem as you. Apparently there is some configuring you need to do in your browser and such.
I forgot that comcast used proxy's.
There's your answer-- IE does a auto config. Mozilla (Older ver's) can not.
Wow, didn't see that one coming. Sorry it's taken so long to reply.
I'm sorry if I'm not much help, I've been looking for a solution... Then I realized-- I have no clue what Yast is.
Mind going into detail?
Perhaps the problem is there.
I haven't been using Linux for very long -- So you may just be wasting your time with me. I'll try to help you out though.
are you setting up eth0 or eth1 with dhcp, in slack i had the same problem(yes i know differant distro) till i figured out that slack wanted eth0 to be loopback and eth1 to be my accual lan card and just wouldnt have it any other way, also be ABSOLUTLY SURE your nic is supported in your kernel and if not set it up in the kernel , recompile, make backup of current kernel,(or add path to newly configured and compiled kernel to lilo for a nice easy way to choose the kernel to boot with and reboot.