Author Topic: Should I run this command?  (Read 2872 times)

Offline ElCuervo

  • Hero Member
  • *****
  • Posts: 4148
  • I'm walking on sunshine!
Re: Should I run this command?
« Reply #15 on: February 07, 2011, 10:16:21 AM »
Could open PCC>Network and Internet
and remove your connection and then setup a new one.

Tried that multiple times, no joy.
It always fails to connect and errors with connectivity issues.
Seems strange since it sees the wireless networks just fine.
Usually, if the NIC sees the network but can't connect, there is a security issue, usually a wrong password. I just fixed one yesterday by re-entering the password, even thought the owner was "absolutely sure" that he had the right one entered on his laptop. I removed the tick mark from "hide password" and it was clearly wrong.

Just to make sure that's NOT the problem, you could try temporarily removing the security setting on your router if all else fails.
"If there were no change, there would be no butterflies" - Walt Disney

http://linuxcounter.net/cert/433721.png

Offline saltcedar

  • Full Member
  • ***
  • Posts: 66
Re: Should I run this command?
« Reply #16 on: February 07, 2011, 10:20:28 AM »
I just fixed one yesterday by re-entering the password, even thought the owner was "absolutely sure" that he had the right one entered on his laptop. I removed the tick mark from "hide password" and it was clearly wrong.

Just to make sure that's NOT the problem, you could try temporarily removing the security setting on your router if all else fails.
Sorry, wish it were so simple. I copied and pasted it from a text file that's
been around for more than a year. All other wireless devices can still
connect using that password.
« Last Edit: February 07, 2011, 10:26:11 AM by saltcedar »

Offline ElCuervo

  • Hero Member
  • *****
  • Posts: 4148
  • I'm walking on sunshine!
Re: Should I run this command?
« Reply #17 on: February 07, 2011, 10:27:31 AM »
I just fixed one yesterday by re-entering the password, even thought the owner was "absolutely sure" that he had the right one entered on his laptop. I removed the tick mark from "hide password" and it was clearly wrong.

Just to make sure that's NOT the problem, you could try temporarily removing the security setting on your router if all else fails.
Sorry, wish it were so simple. I copied and pasted it from a text file that's
been around for more than a year. All other wireless devices can still
connect using that password.

Same thing I heard yesterday. Anyway, good luck with it.
"If there were no change, there would be no butterflies" - Walt Disney

http://linuxcounter.net/cert/433721.png

Offline Ramchu

  • Hero Member
  • *****
  • Posts: 1588
Re: Should I run this command?
« Reply #18 on: February 07, 2011, 10:28:34 AM »
ElCuervo - Thank you for coming here I don't have wireless but was trying to help until
someone else with more knowledge came along.
Quote

Read this but not clear how this applies to my situation


Wanted you to run the command form the last post

Offline saltcedar

  • Full Member
  • ***
  • Posts: 66
Re: Should I run this command?
« Reply #19 on: February 07, 2011, 10:30:03 AM »

Wanted you to run the command form the last post

Will do.

New wrinkle?

When I connected over Ethernet it prompted me for a root password.
Maybe I have a permission's issue?

Offline saltcedar

  • Full Member
  • ***
  • Posts: 66
Re: Should I run this command?
« Reply #20 on: February 07, 2011, 10:32:10 AM »
Feb  7 11:25:28 localhost dhclient: DHCPACK from 192.168.1.254
Feb  7 11:25:28 localhost klogd: martian source 255.255.255.255 from 192.168.1.254, on dev eth0
Feb  7 11:25:28 localhost klogd: ll header: 00:26:9e:23:e1:94:00:1b:5b:df:1b:01:08:00
Feb  7 11:25:28 localhost avahi-daemon[2912]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.73.
Feb  7 11:25:28 localhost avahi-daemon[2912]: New relevant interface eth0.IPv4 for mDNS.
Feb  7 11:25:28 localhost avahi-daemon[2912]: Registering new address record for 192.168.1.73 on eth0.IPv4.
Feb  7 11:25:28 localhost NET[8719]: /sbin/dhclient-script : updated /etc/resolv.conf
Feb  7 11:25:28 localhost dhclient: bound to 192.168.1.73 -- renewal in 38668 seconds.
Feb  7 11:28:40 localhost ntpd[3804]: Listening on interface #6 eth0, fe80::226:9eff:fe23:e194#123 Enabled
Feb  7 11:28:40 localhost ntpd[3804]: Listening on interface #7 eth0, 192.168.1.73#123 Enabled
Feb  7 11:28:40 localhost ntpd[3804]: new interface(s) found: waking up resolver
Feb  7 11:28:42 localhost ntpd_initres[3821]: host name not found: 0.us.pool.ntp.org
Feb  7 11:28:42 localhost ntpd_initres[3821]: host name not found: 1.us.pool.ntp.org
Feb  7 11:28:42 localhost ntpd_initres[3821]: host name not found: 2.us.pool.ntp.org
Feb  7 11:29:17 localhost nmbd[2855]: [2011/02/07 11:29:17.068784,  0] nmbd/nmbd_become_lmb.c:395(become_local_master_stage2)
Feb  7 11:29:17 localhost nmbd[2855]:   *****
Feb  7 11:29:17 localhost nmbd[2855]:   
Feb  7 11:29:17 localhost nmbd[2855]:   Samba name server LOCALHOST is now a local master browser for workgroup HOME on subnet 192.168.1.73
Feb  7 11:29:17 localhost nmbd[2855]:   
Feb  7 11:29:17 localhost nmbd[2855]:   *****

Offline saltcedar

  • Full Member
  • ***
  • Posts: 66
Re: Should I run this command?
« Reply #21 on: February 07, 2011, 10:56:26 AM »
All other wireless devices can still
connect using that password.

Same thing I heard yesterday. Anyway, good luck with it.

 Not sure how to respond to this. Yes, I checked it was identical.
Like you I thought I might have only copied part of the password
but it's all there and that file hasn't been changed.

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: Should I run this command?
« Reply #22 on: February 07, 2011, 12:05:57 PM »
Feb  7 11:25:28 localhost avahi-daemon[2912]: Registering new address record for 192.168.1.73 on eth0.IPv4.
Feb  7 11:25:28 localhost NET[8719]: /sbin/dhclient-script : updated /etc/resolv.conf
Feb  7 11:25:28 localhost dhclient: bound to 192.168.1.73 -- renewal in 38668 seconds.
Feb  7 11:28:40 localhost ntpd[3804]: Listening on interface #6 eth0, fe80::226:9eff:fe23:e194#123 Enabled
Feb  7 11:28:40 localhost ntpd[3804]: Listening on interface #7 eth0, 192.168.1.73#123 Enabled
Feb  7 11:28:40 localhost ntpd[3804]: new interface(s) found: waking up resolver
Feb  7 11:28:42 localhost ntpd_initres[3821]: host name not found: 0.us.pool.ntp.org
Feb  7 11:28:42 localhost ntpd_initres[3821]: host name not found: 1.us.pool.ntp.org

From what I see in your log, the inferface connect to to the router and obtain address from dhclient brown marked lines),
then fails to contact ntp server (red marked line) probably because of a problem related to DNS settings.

Try to check DNS settings, both on router, on PCC, and eventually refer to another running computer.
After connection try to look in /etc/resolv.conf.
Look like you have IPv6 enabled, try to disable IPv6 for now.

AS, HTH

Offline saltcedar

  • Full Member
  • ***
  • Posts: 66
Re: Should I run this command?
« Reply #23 on: February 07, 2011, 02:31:12 PM »
localhost is my domain name.
I never set a domain (workgroup under samba is HOME)
I get an error in PCC says Need FQDN.

Terrific where do I get it and why was it changed in the first place?

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: Should I run this command?
« Reply #24 on: February 07, 2011, 02:49:25 PM »
localhost is my domain name.
I never set a domain (workgroup under samba is HOME)
I get an error in PCC says Need FQDN.

Terrific where do I get it and why was it changed in the first place?

No, you don't need to check or change your computer's name and/or domain name,

you need to search in your network configuration parameter (PCC / Network center / Your card / Configure) the flag marked as "Get DNS server from DHCP",
and to mark as "checked" this flag.

if doesn't work, please post the content of the file /etc/resolv.conf

AS


Offline saltcedar

  • Full Member
  • ***
  • Posts: 66
Re: Should I run this command?
« Reply #25 on: February 07, 2011, 03:01:47 PM »
Closest match I can find for /etc/resolv.conf
 is /etc/resolvconf which contains resolv.conf.d

That contains the following...

file:///etc/resolvconf/resolv.conf.d/base
file:///etc/resolvconf/resolv.conf.d/head
file:///etc/resolvconf/resolv.conf.d/tail

No doubt I'm in the wrong directory but
no clue where to hunt. BTW Get DNS server from DHCP was checked

Offline Ramchu

  • Hero Member
  • *****
  • Posts: 1588
Re: Should I run this command?
« Reply #26 on: February 07, 2011, 03:07:50 PM »
I can see the file in my system
open file manager>root>etc> scroll almost to the bottom is a file not a folder.

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: Should I run this command?
« Reply #27 on: February 07, 2011, 03:12:43 PM »
saltcedar,

check if resolvconf service is running too,
you'll find it in PCC -> System -> Manage System services ...

Offline saltcedar

  • Full Member
  • ***
  • Posts: 66
Re: Should I run this command?
« Reply #28 on: February 07, 2011, 03:20:00 PM »
I can see the file in my system
open file manager>root>etc> scroll almost to the bottom is a file not a folder.

Doh!

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.1.254
search gateway.2wire.net




resolvconf service is running.
« Last Edit: February 07, 2011, 03:24:43 PM by saltcedar »

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: Should I run this command?
« Reply #29 on: February 07, 2011, 03:28:51 PM »
from command line (Konsole, xterm. whatever you prefer) try the following two commands:

ping ntp1.linuxhosted.ca
ping 72.20.40.62

report back about both results