Can access the network but not the internet

[HailandKill]

Running Fedora Core 4.

The machine can access the rest of the network fine, but it is refusing to connect to the internet.

All the other machines on the network (running windows) have no problem.

The network is connected to broadband internet via a router.

A small while ago, I was trying to connect to the internet on another network via proxy. This also didn't work but that was due to external reasons. Since then, I have changed all the settings back to "Direct connection to the internet". At least, all the settings I know of.

I don't know if this is related at all but, although I said the network is working fine, I was just trying to move a screen shot of ifconfig over to this computer and while I can access this computer from my linux machine and I can pull files from it, Fedora Core reports:

Error "Access Denied" while copying x
Would you like to continue?

When I try to move files the other way, from the linux machine to this one. Where x is anything I try to copy accross the network. Although the file has all permisions granted (i.e. 777).

EDIT:

I remember something else I did a long time ago, I changed the hostname from localhost.localdomain to bglaptop.localdomain. I assumed that would just be like changing the computer name like in windows. On booting up again though, I got some error message that I cannot remember. So I changed it back to localhost.localdomain.

On that note, not long after I did all that openoffice gave me the following error:

Either another instance of OpenOffice is accessing your personal setting or your personal settings are locked.

Simultaneous access can lead to inconsistencies in your personal settings. Before continuing, you should make sure that 'root' closes OpenOffice.Org on host localhost.localdomain

I think that is what promted me to change the name back to localhost.localdomain

Are all these things possibly connected?

[mikesull]

I also have just recently installed FC4 on my system and have the same problem. I have a dual boot system with windows XP on the other side. I am also using a DSL router (cheap Actiotec) using dhcp. In XP the internet works fine, and I can even connect to some sites in FC4 as well as ping any IP address I want. I've been searching other forums and it seems that Fedora has a problem when using a router w/ dhcp. It seems ipv6 is the root cause according to the other posts I've read. Other users has said they needed to change config files to shut off ipv6 to fix the problem. I'm still trying to find an easier way or patch to fix this as I 'm not the greatest with networking. I will repost when I find any more info.

[Zotter]

Two obvious things to check:

That box's default IP route and it's DNS resolvers

Use the 'route' command to see what's up with default routing - your default gateway should be your gateway router (actiontech defaults to 192.168.0.1). Your default route is the last line of the output from 'route' and labled such.

File /etc/resolv.conf (use 'cat /etc/resolv.conf' to see it) will show what your resolvers are set to. Likely set by DHCP to point to your router.

Try 'nslookup - <DNS IP>' where <DNS IP> is your ISP's DNS servers. ie. 'nslookup - 199.190.151.1' this will return a prompt where you can type in names and get their IPs from the indicated DNS server. Drop in a few names, make sure you can resolve them. Once you know your DNS is setup right, ensure your actiontech is relaying DNS properly - do the same deal, but point at your router as the resolver 'nslookup - 192.168.0.1' and try the same names. Type 'exit' to get out of it.

You can skip DNS relay through the router and point directly to your ISPs DNS servers if you want. Of course, that will mean fiddling with your DHCP client or network settings so /etc/resolv.conf isn't re-written at every startup.

Check out NET3-4 how-to (http://www.tldp.org/HOWTO/NET3-4-HOWTO.html) at tldp.org for more details.

[Zotter]

To disable IPv6:

To disable IPV6: As root, you must add the line: "alias net-pf-10 off" (without quotes)
to the end of your /etc/modprobe.conf file.

[root@charon root]# echo "alias net-pf-10 off" >> /etc/modprobe.conf

A reboot is required.



That's an edited 'cut n paste' from the EXCELLENT FC setup guides found at:
http://www.mjmwired.net/resources.php

Info on IPv6 is from the FC2 guide.

[mikesull]

Thanks for the info. I'm at work right now and I'll try somethings when I get home tonight. I found this info in another post today which I might use, check it out:




DSL Actiontec modem...fix!
Okay, so...for days and days I've tried to make my Actiontec DSL modem (provided by Qwest) to work in linux...on kernel 2.6. I have FINALLY found a solution, after trying several times...and failing miserably. As some of you know...with this modem you can ping, and you do indeed recieve packets back, but you cannot browse any website on any web-browser. This is because on kernel 2.6, for whatever reason, DHCPCD detects the wrong nameservers. If you check your /etc/resolve.conf...you will see that the first nameserver is actually your ip number.

Anyway...type in 192.168.0.1 into your browser and hit enter to goto the actiontec gateway setup script. Click setup...and then click "Non Windows Setup". Click PPPoA or PPPoE...whichever one applies to you. Enter your username and password...and click "Save and Restart". Wait for your modem lights to stop blinking...and make sure that your internet light comes on.

Next...open up your resolve.conf file. Enter the two correct nameservers in it, and save the file. You will notice now, that you can browse (or atleast I could.) Problem is, when you restart...dhcp will automatically detect the wrong settings again, and overwrite your correct resolve.conf file. To prevent this from happening...find your inet1 file, and open it up in your favorite editor. I just opened it up in kwrite...so I could easily find dhcp with control + f. For me, this file is in /etc/rc.d/rc.inet1. Now...press Control+f and type in DHCP and press enter. IT will then jump down to this area:

Quote:
if [ "${USE_DHCP[$1]}" = "yes" ]; then # use DHCP to bring interface up
if [ ! "${DHCP_HOSTNAME[$1]}" = "" ]; then
echo "/etc/rc.d/rc.inet1: /sbin/dhcpcd -d -t 10 -h ${DHCP_HOSTNAME[$1]} eth${1}" | $LOGGER
/sbin/dhcpcd -d -t 10 -h ${DHCP_HOSTNAME[$1]} eth${1}
else
echo "/etc/rc.d/rc.inet1: /sbin/dhcpcd -d -t 10 eth${1}" | $LOGGER
/sbin/dhcpcd -d -t 10 eth${1}

After each of your /sbin/dhcpcd lines...add a -R flag. This will make it so your resolve.conf will not be overwritten with the incorrect nameservers again. Reboot...and if all goes well, your resolve.conf file will stay correct, and you will now be able to browse without any problem .

If this sounded extremely "noobish"..please forgive, I am still very much learning...yet fixing this problem was a huge success/learning experience for me. I also noticed, that when searching for problems like mine on these forums, it seemed that no one knew the answer to fix this problem. I hope this helps someone else like it helped me.

-RoaCh

[mikesull]

This is what I did to solve my problem:

I logged into my router with my browser, (I just typed 192.168.0.1, most routers are generic i. e. 192.168.1.1, ect. ect., then wrote down my IP info (especially the DNS sever IPs).

Then I opened a terminal and used nslookup as directed by Zotter. My DNS IPs from my internet service provider resolved with a handfull of naming servers. I THEN JOTTED A FEW OF THESE DOWN (you will need a few of these addresses to resolve the issue - THESE MUST BE THEIR NUMBER FORM -obviously).

(FYI- I tried nslookup on my router's IP and IT DID NOT RESOLVE. Another note: Try pinging a website, and then jot down the numerical ip for the website. Enter that into your browser and see what happens. The pages I couldn't get to using the name worked when using the raw ip addresses).

So this is the final step:
so I edited the file /etc/resolv.conf like this (you'll probably need to be logged in as root, as this file is protected):
BEFORE-
; generated by /sbin/dhclient-script
search domain.actdsltmp
nameserver 192.168.0.1
nameserver 198.6.1.3

AFTER -
; generated by /sbin/dhclient-script
search tds.net MY ISP
nameserver 204.246.0.9 NAME SERVER I JOTTED DOWN WHILE RUNNING NSLOOKUP
nameserver 66.173.0.4 NAME SERVER I JOTTED DOWN WHILE RUNNING NSLOOKUP

Now everything works great. I did not have to do any other editing of any other files as mentioned earlier. I rebooted my PC and the resolv.conf stayed the same.