skype working but can't web browse or ping, dns issue ?

Asked by Jacques Malaprade

Hi,
I have been looking for a solution to this problem since yesterday. It seems like skype will work on my desktop but I can't browse the internet or even ping another IP address. I am using my laptop which is connected to the router to send this message.
I have recently set up the laptop and desktop in a home network. The wireless router is plugged into the desktop, and the laptop is connected to the router via wireless. The laptop and desktop network is working well using nfs and even remote desktop, the laptop can go on the internet and and do everything that is needed, but the desktop will only skype and nothing else.
I have even tried another browser (IE in wine - I normally use firefox) and this also doesn't work, so the problem can not be the browser setting (I think). Pinging another IP address also does not provide a response.
I am relatively new to ubuntu and trying my best with my limited knowledge. Help will be much appreciated.
Jacques.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu gnome-nettool Edit question
Assignee:
No assignee Edit question
Solved by:
Jacques Malaprade
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Can you ping 8.8.8.8 ?

Revision history for this message
Ian Ace (iaculallad) said :
#2

Can you try disabling IPv6 in your Firefox browser: On Firefox's address bar, type in the line below and press Enter key:

about:config

and change the value of network.dns.disableIPv6 value to 'True'.

HTH.

Revision history for this message
Jacques Malaprade (malapradej) said :
#3

Hi,

Thanks for getting back so soon.

The ping is working to 8.8.8.8!

network.dns.disabledIPv6 was set to true before. It was part of my struggles to get it working... That is why I think it is not a firefox problem, but I could be wrong.

Needless to say despite the ping the browser is still not working:(

Jacques

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#4

Ok then run:

gksudo gedit /etc/resolv.conf

delete all the text in the file and add these 2 lines:

nameserver 8.8.8.8
nameserver 8.8.4.4

Save the new file and close gedit. Does the web work ok?

Revision history for this message
Ian Ace (iaculallad) said :
#5

After making changes on your resolv.conf file, you might try restarting your networking daemon:

sudo /etc/init.d/networking restart

HTH.

Revision history for this message
Jacques Malaprade (malapradej) said :
#6

Hi,

I have done and saved the edits to resolv.conf and without restarting the network the browser started working. Just to check that it didn't affect the home network I tried access the shared folders on the desktop, and that worked as well, also I could use remote desktop viewer on both the laptop and desktop.
As soon as I rebooted both PC's the problem reoccurred. When I open the resolv.conf file it seems like the content had been erased. Now no matter if I edit the content of resolv.conf and restart the network (as described above), it comes up with "WARNING: ifup -a is disabled in favour of NetworkManager, Set ifupdown:managed=false in /etc/NetworkManager/nm-system-settings.conf."
I have not changed this setting as I don't know how this will affect my nfs network or remote desktoping.
Sorry to be a pain, but I would like to get this working.

Jacques

Revision history for this message
Jacques Malaprade (malapradej) said :
#7

After rebooting both PC's it still seems like he content of the resolv.conf file has been cleared. The home network works but the desktop web browser does not work.

Revision history for this message
Ian Ace (iaculallad) said :
#8

Try the solution below:

a. Make a backup of the file we are about to edit:

sudo cp /etc/dhcp3/dhclient.conf /etc/dhcp3/dhclient.conf.bak

b. Edit /etc/dhcp3/dhclient.conf

gksudo gedit /etc/dhcp3/dhclient.conf

c. Search for the line which reads:

#prepend domain-name-servers 127.0.0.1;

Uncomment it. Remove the # and edit it to look like the line below:

prepend domain-name-servers 8.8.8.8;
prepend domain-name-servers 8.8.4.4;

d. Search for the domain-name-servers, and comment (add the # character before the line) it:

prepend domain-name-servers 8.8.8.8;
prepend domain-name-servers 8.8.4.4;
request subnet-mask, broadcast-address, time-offset, routers,
        domain-name, domain-name-servers, host-name,
        netbios-name-servers, netbios-scope;
#require subnet-mask, domain-name-servers;

e. Save and Close the file. Restart the networking daemon and test it.

sudo/etc/init.d/networking restart

f. If it works, try restarting your unit and observe check if it retains the working settings.

HTH.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#9

Could just add it in network manager, set the interface to dhcp (address only) then set the dns address manually. I guess with a forum it is better to use text based help.

With the connection up you can update which may make the system set DNS via DHCP as it should.

Revision history for this message
Jacques Malaprade (malapradej) said :
#10

Hi have done just this and it came up with the following:

* Reconfiguring network interfaces...
SIOCDELRT: No such process
WARNING: ifup -a is disabled in favour of NetworkManager.
  Set ifupdown:managed=false in /etc/NetworkManager/nm-system-settings.conf.

Should I change the setting in the network manager? Also, please explain how to do this as well as the steps you described above.

Many thanks,

Revision history for this message
Jacques Malaprade (malapradej) said :
#11

Hi have rebooted the desktop and can't web browse or communicate with the laptop.

I have reset managed=true and rebooted as at least then the home network is working.

Hope this can be resolved. Many thanks for your time.

Revision history for this message
Jacques Malaprade (malapradej) said :
#12

I am a bit lost. Ian, actionparsnip, is aybody online? Sorry to have taken so long on the last reply. Kids duty...

Revision history for this message
Jacques Malaprade (malapradej) said :
#13

Just to note I have researched a bit further and it seems to be problem that the resolv.conf file gets overwritten after every reboot. I thus tried to amend the dhclient.conf file as this seems to override the amendments to resolv.conf. The complete file is attached below:

option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;

send host-name "<hostname>";
#send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
#send dhcp-lease-time 3600;
#supersede domain-name "fugue.com home.vix.com";
prepend domain-name-servers 8.8.8.8, 8.8.4.4;
request subnet-mask, broadcast-address, time-offset, routers,
 domain-name, domain-name-servers, domain-search, host-name,
 netbios-name-servers, netbios-scope, interface-mtu,
 rfc3442-classless-static-routes, ntp-servers;
#require subnet-mask, domain-name-servers;
#timeout 60;
#retry 60;
#reboot 10;
#select-timeout 5;
#initial-interval 2;
#script "/etc/dhcp3/dhclient-script";
#media "-link0 -link1 -link2", "link0 link1";
#reject 192.33.137.209;

#alias {
# interface "eth0";
# fixed-address 192.5.5.213;
# option subnet-mask 255.255.255.255;
#}

#lease {
# interface "eth0";
# fixed-address 192.33.137.200;
# medium "link0 link1";
# option host-name "andare.swiftmedia.com";
# option subnet-mask 255.255.255.0;
# option broadcast-address 192.33.137.255;
# option routers 192.33.137.250;
# option domain-name-servers 127.0.0.1;
# renew 2 2000/1/12 00:00:01;
# rebind 2 2000/1/12 00:00:01;
# expire 2 2000/1/12 00:00:01;
#}

But even this does not make the changes permanent. Every time I reboot resolv.conf is wiped.

I hope someone sees the answer...

Revision history for this message
Jacques Malaprade (malapradej) said :
#14

Hi,

Wonder of wonders I seem to have resolved the problem. Although I don't see the NetworkManager applet on the panel.

All I did was change /etc/NetworkManager/nm-system-settings.conf to read:

[ifupdown]
managed=false

Thanks,