It'd be easier to follow this if you didn't abbreviate words
so much
that I have to guess at what you're referring to.
Will try not to use
abbreviations at all.
My next guess is that the 10 digit key is a pass key for
authenticating
over an encrypted network, as many wireless links are, and should be.
Unencrypted wireless, or inadequately encrypted, is a major security
problem.
Perhaps that device comes with a preconfigured access key, rather
than
requiring you to enter your own personal keys into both sides of the
connection (router, and client computers).
I don't really understand your response here.
To repeat, the imac is working, apparently with full internet access,
via *wired* connection. The prior use of wireless internet on the imac,
has been turned off.
> Evidently necessary electronics parts needed for the uverse
setup.
> I only noticed them after the tech left.
Hmm, well, if you can't tell us what they are, we can't offer
any advice
about them. Whether they have anything to do with the issues, or not.
Are they power supplies for the rest of the devices, DSL/phone line
separation filters, soemthing else?
will try to get sensible answers from att, will reply on that later.
> that 64.94.156.1 is no good, or stale, or???
Is probably wrong.
YES, sorry, 'just' a typo on my part,
it has always been 68.94.156.1
which seems to say both of the DNS numbers I am using are valid.
For what it's worth, sometimes you can find out the name servers
for
your ISP, by yourself. It's common for name servers to have a "ns"
hostname in front of their domain name. So, if I wanted to find out the
nameservers for a ficticious
example.com ISP, I could try doing a query
like: dig
ns.example.com Likewise, I could try
ns1.example.com or
ns2.example.com, to see if they have other name servers, too.
But, like I said
earlier on, if you have a wrong name server address in your resolv.conf
file listed before it, you will have problems.
If you have wrong data in resolv.conf file, restarting NetworkManager
may cause your system to set up the network connection again, and find
out which DNS servers to use. It'll probably rewrite the resolv.conf
file, and you can look for any changes to it.
This now appears not so, i.e. the data in resolv.conf appear correct.
bash-3.2$ dig
ns1.pacbell.net
; <<>> DiG 9.6-ESV-R4-P3 <<>>
ns1.pacbell.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2897
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;ns1.pacbell.net. IN A
;; AUTHORITY SECTION:
pacbell.net. 7200 IN SOA
ns1.pbi.net. postmaster.pbi.ne\
t. 2012100300 3600 900 604800 7200
;; Query time: 1071 msec
;; SERVER: 192.168.1.254#53(192.168.1.254)
;; WHEN: Wed Oct 3 09:26:10 2012
;; MSG SIZE rcvd: 88
Does this tell me anything? is
ns1.pbi.net a DNS number I could/should use?
In addition to the two I now have?
I did pull the new modem power cable,
after plugging back in the system took a while to come fully on.
No help on internet:
trying to start google chrome, still getting message invalid DNS.
It seems I don't need to correct faults in the DNS numbers,
so does it still make sense to restart NetworkManager?
Exactly how would I restart it?
-- chkconfig?
-- some systemd command?
I did pull the new modem power cable,
after plugging back in the system took a while to come fully on.
No help on internet:
trying to start google chrome, still getting message invalid DNS.
thanks much for your continuing responses.
Jack