Still unable to connect to internet using Comcast Cable and Mandriva
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Still unable to connect to internet using Comcast Cable and Mandriva
Hi, I posted this problem about a month ago and tried the suggestions offered but have had no luck.
I had internet service for Mandriva via Embarq DSL but have moved to location that only has Comcast.
I'm using a Dell Optiplex 270 PC with an Intel Pro Gigabit network card. I've tried connecting to Comcast via a router and directly but in either case I've had no success. The router I'm using is a Linksys Model BEFSR41 v.2.
What I'm trying to do seems simple enough. I've been going to the "configure your computer" menu item, deleting my network connection and setting up a new one. When setting a new connection, I've chosen the "automatic" option letting the computer pick a DHCP address, etc... and I've chosen the "static" option, inputting my own IP address info (I think I've found the right IP address for my computer). In either case I've not been able to reach the internet, although when I choose the "static" option and input my own IP address, the computer says the network connection is operating (and the little "connection icon" at the bottom of the screen shows a connected symbol), but I still can't reach any internet destinations through my browser (Firefox).
I'd appreciate any ideas anyone has -- my wife is looking at the situation practically and says "maybe we should put Windows on that compter if we can't get to the internet with Linux." If I can't get Linux to work with Comcast, I'll probably have to do what she says.
Setting up an IP for your computer is only part of the procedure. You will also need to configure your gateway and DNS settings. Chances are, your router will have an address such as 192.168.0.1 or 192.168.1.1 (check your documentation)
You will need to give your PC an IP address in the proper range (192.168.0.xxx or 192.168.1.xxx) if not already configured properly. You will then need to add your gateway and DNS to your Linux network configuration as well... (the IP address of your router)
Chances are, what is happening is that your computer can "see" the network, but is having problems resolving web addresses. Without being able to resolve, it will just sit there and not really go anywhere...
I have successfully set up Linux machines using Comcast before. Granted, it was using SuSE or Ubuntu, but I can't see that Mandriva should be much different.
You might also need to check the settings on your broadband modem. It may need to be set to bridge mode if you are using your router to control access to the internet. The router and modem may be fighting each other. I have run into this setting up some networks for DSL, but I haven't had as much experience with cable modems and am unsure as to weather they operate the same way as DSL modems do. (ie: needing to be set to bridge mode)
Thanks for the replies. I need to ask a couple of more questons.
"Setting up an IP for your computer is only part of the procedure. You will also need to configure your gateway and DNS settings."
Do you mean gateway and DNS settings for the router or computer? Also, it's slightly embarrasing to admit but I don't really know what the terms gateway and DNS mean. (Just used to the world of plug and play and not learning about the details).
I actually had to call my cable provider and go through a manual setup process where they registered the Modems Serial Number and MAC address into their system before I could get internet access.. typically that procedure is done with their "internet setup wizard" that comes on a CD with the internet package, but of course that only runs on Windows...
They had also insisted their tech come out to do the install.. Wife was home so I left my Linux PC unlocked and told her to let him 'have at it' since I would be at work. Of course when I got home after work it wasn't done, the tech gave up before he even started since it was not Windows.. heh i still don't knwo why HE didn't call in and do the manual modem registration for me..
The way it works is that your computer can have it's own IP address. (such as a street address for your house...)
The network will have a range of addresses. (such as different addresses on each house in your neighborhood...)
Each PC will have it's own unique network address, as will your router. You can think of the router as the middle hub of a wagon wheel with spokes going out to each PC. Each PC will go through the router to get to the outside world. The router is the "gateway" to the internet.
Now, if you use DHCP, the router will give out addresses to your computers on the network automatically. It will configure your network settings to point to itself as your gateway and DNS (Domain Name Server). (Think of a DNS as a phone book with the number for all of the web sites out on the internet.) And things are usually pretty much good to go.
However, if you manually set network addresses, you will need to configure your network settings on your computer manually to point to your router as the gateway and the name server. Otherwise, your computer will be requesting information, but won't know where to go to send/receive from the outside world.
Usually, the router address will be in the private range. Something like 192.168.1.1
So, you will set up your computer with an IP address such as 192.168.1.10, configure your gateway as 192.168.1.1, and the DNS as 192.168.1.1 as well.
I usually will check the logs on my router to see what DNS settings my ISP dishes out, and I will add a couple of those DNS entries as secondary or tertiary DNS entries on my PC's network settings. (Just in case the router has issues resolving...)
I would try using DHCP first and see if that fixes your problems. If so, it is most likely only a matter of filling in the blanks with the proper numbers if you go manual. If the DHCP doesn't fix it, there may be other problems such as the router and modem "fighting", or maybe a bad NIC or network cable.
It is normally frowned on to start a new thread rather than simply continue the exisiting one. But let's just stay with this one.
With a router (good thing to have), you have to setup two different things:
1. Setup the router to use the internet connection settings provided by your ISP--almost certainly DHCP.
2. Setup the router (and computer) for connection on the local network. Here also, DHCP is a common choice.
To configure the router, start by setting your computer for dhcp (almost certainly the router default), and accessing the router using 192.168.1.1 in a browser. This should give you the router configuration page. The router manual will give you all the instructions for this.
When you have a router, there should be no issues with the Comcast internet connection---the cable modem sees only a generic router, and never knows that Linux is on the other side. If, for example, Comcast tech support tried to say that Linux was the problem, politely explain that--with a router--that cannot be the issue.
Finally, if you have any trouble getting to the router configuration page, simply try with another computer.
Finally, finally: Take the time to learn how all this works. It would be really counterproductive to simply switch to Windows to solve the issue. What if you have problems in Windows also.
"It is normally frowned on to start a new thread rather than simply continue the exisiting one. But let's just stay with this one."
I'm sorry, I don't get onto forums very often, so I don't know the etiquette -- I thought since the thread was old, no one would want to check it anymore, now I know better.
"Finally, finally: Take the time to learn how all this works. It would be really counterproductive to simply switch to Windows to solve the issue. What if you have problems in Windows also."
You're right. I have to use Apple Macintosh on my job -- I work as a video editor. I have to use a PC to communicate with other people in our organization. I'd love to spend time learning Linux, as well as how to operate Windows and the Mac OS better, but as it is, I just get by with all of them. Linux provides my best chance at actually learining something about an OS because there's a big community of users who share information. I'll try to squeeze in some time to become more versed but that will probably mostly involve a lot of asking questions at the Linux forum when I run into trouble.
When I setup a computer locally I will setup a static IP first. I do as root from cli;
~#ifconfig -a #get recognized devices
~#ifconfig eth0 192.168.0.10 #set to a available IP
~#route add default gw 192.168.0.1 #set to your gateway
~#route -n #show the route table
~#ifconfig eth0 up #should be up already
~#ping 192.168.0.1 #ping your gateway
~#ping 184.108.40.206 #google.com IP
~#ping google.com #test DNS, if fail then
Be sure to use IPs that are in your subnet.
You should have your '/etc/resolv.conf' setup with your 'ISP DNS' nameservers.
verizon third level dns;
You could include the above in your '/etc/resolv.conf' file. I do place after my ISP assignments. I've also placed before the ISP assignments too see if there is a difference.