Hi all,

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:

D-Link DFE-530TX+

The motherboard is SOYO: SY-P4IS2


Everything looks perfect from Yast, but when I push Finish, I'm gettiing nothing!!

Your advice will be greatly appreciated!!

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.

Look at this post for a solution
http://www.linuxquestions.org/questi...hreadid=123413

I appreciate the hints abou the browser (in my case Konqueror) and I'll try them.

However, yesterday I starting suspecting that there might be some misconfiguration overlooked by Yast. So I tried o couple of things on the command line:

"ifconfig" gave me no errors for my NIC. Also, the driver is up and running.

BUT, several options of "dhcpcd" (including -H) froze up or gave me "script stopped" or something like that.

So, I tried a testing utility that came with SUSE: "dhcping" with options -c, -g and also -h. In every case I got this message: "bind:Address already in use".

So, my hypothesis that there's something incorrect in dhcp management is still tenable. What do you think?

I'll try what I've read today and I'll let you know (for truth's sake). Thank you


Xri

I tried the advice regarding Mozilla. After installing it, I modified the proxy setting according to the directions from the other posting and nothing happened.

I tried many different settings with dhcpcd and nothing worked.

Then I installed ddclient and played with different configurations and requests and all worked as if the cable connection was dead.

Finally, I installed dhclient and worked making changes on the configuration file (supposedly made to help cable connections). I always had the same final result: NO LEASE OFFER.

I find no other solution than taking either DSL or dial up.


Xri

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.

then proceed as normal and see what happens.