If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#16
|
|||
|
|||
"Acquiring network address" - what gives?
In message , Mike Easter
writes: Paul in Houston TX wrote: I've never had a modem / router or separate modem and router last more than 2.5 years. Quite some years ago, Win95 days, cable modems were bigger and got much hotter and didn't last long. My provider had to replace it regularly. Those years I couldn't own my own and also there was no monthly fee for the modem. These days my cable modem is smaller and cooler and has lasted for years and years. Likewise my low priced router. But... if I don't have a spare router on hand 'at all times' I watch carefully for router sales and buy one 'in advance' to have a spare. The price of routers on sale is much cheaper than having to buy a router when you have to have it. The one I'm using was bought in that way - cheapest I could find then. It's worked for years. It clearly wasn't that at fault anyway - the other PC (a 7) was still working fine through it, and rebooting this one made it work for a while. After doing a system restore to four days ago, the link has remained up overnight. Which is reassuring in one way, but worrying in another, in that I'm unaware of having done anything (changed any settings) recently that I can think of that would have changed anything and made it unreliable. -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf Experience is the comb life gives you after you lose your hair. -Judith Stearn |
Ads |
#17
|
|||
|
|||
"Acquiring network address" - what gives?
Paul in Houston TX wrote:
Thanks Paul. Good advice that I will remember (and write down). Working up a beer can is too much work :-) You'll need to drink another beer when you're finished. Oh. Paul |
#18
|
|||
|
|||
"Acquiring network address" - what gives?
The problem is back, sort of.
This machine so far has usually connected to the wifi router on a reboot, which connection then remains sound for ages (hours, or a day or two); I then suddenly find the connection has gone, and the tray icon that normally shows a little computer with ")))" next to it is instead showing the little computer with a yellow circle jumping right to left. If I hover over this icon, I get a popup showing Wireless Network Connection (SSID) [the correct SSID] Speed: 54.0 Mbps Signal Strength: Excellent [it's only about 3 yards!] Status: Acquiring network address This is what I normally see while it's establishing connection; but that normally resolves to "Connected" after a short time, and the tray icon goes to ))) (radio waves). It's currently staying at "Acquiring ..." indefinitely. 1. The router/MoDem is working fine; I can access outside web pages via another computer next to this one. (This computer is also connected via wifi, not cable.) 2. The wifi hardware in this machine is receiving, I presume, otherwise I wouldn't get the signal strength reading. (It can see other nearby networks, too. And I don't think any of them are the problem: I'm less than 3 yards from my router.) 3. The wifi hardware in this machine is transmitting: if I access the router's status pages (via 10.0.0.2) on the other machine, I can see this machine's MAC listed in the list of devices connected (there are only two, this machine and the other one), which disappears and then reappears if I manually disconnect and then (attempt to) reconnect this machine. So it seems to me, it's something at a higher level - part of XP - that's "gone peculiar"; the hardware seems to be both receiving and transmitting. Any suggestions as to how to prod it, other than rebooting? (Or ideally fix the problem, of course, but I'd live with having to do a prod.) It's very odd; if I disconnect (right-click on tray icon, View Available Wireless Networks, click on the one - which is showing Acquiring network address - and click Disconnect, then Yes), then reconnect (select the appropriate network from the list [which refreshed itself when I disconnected] and click Connect, then again on the password screen which appears]), it goes back to Acquiring ..., for ever. If I turn it back to automatic (because disconnecting told me it'd turn that off), by selecting "Change the order of preferred networks", selecting the appropriate one, Properties, Connection, Connect when ... on range (which turns it back to automatic), it does the same, i. e. sits at Acquiring ... for ever. I can't "ping" 10.0.0.2 from a command prompt, or access it from a browser. (When connected, I can.) And yet if I reboot, it'll connect fine. (It's just tedious having to do so, of course.) Samsung NC-20 netbook; "Atheros AR5007EG Wireless Network Adapter" it says, and also "This device is working properly"; "This connection uses the following items" has them all ticked. (Besides, it's been working for years.) Final thought - I see under Configure ... Advanced that "Power Save Mode" is set to Normal (the choices being Maximum, Normal, or Off); I could try turning it to Off (I use the machine on external power anyway), but (a) surely if it did power down it ought to reconnect when needed (b) why has it just started happening? Remember: o machine next this one has identical connection that works continuously o hardware is receiving (signal strength, and can see networks) o hardware is transmitting (appears in MAC list) o reboot cures all, possibly for days a puzzling one! -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf So, Heresy be damned (well, it would be, wouldn't it?). Radio Times 24-30 July 2010 (page 24) |
#19
|
|||
|
|||
"Acquiring network address" - what gives?
J. P. Gilliver (John) wrote:
The problem is back, sort of. This machine so far has usually connected to the wifi router on a reboot, which connection then remains sound for ages (hours, or a day or two); I then suddenly find the connection has gone, and the tray icon that normally shows a little computer with ")))" next to it is instead showing the little computer with a yellow circle jumping right to left. If I hover over this icon, I get a popup showing Wireless Network Connection (SSID) [the correct SSID] Speed: 54.0 Mbps Signal Strength: Excellent [it's only about 3 yards!] Status: Acquiring network address This is what I normally see while it's establishing connection; but that normally resolves to "Connected" after a short time, and the tray icon goes to ))) (radio waves). It's currently staying at "Acquiring ..." indefinitely. 1. The router/MoDem is working fine; I can access outside web pages via another computer next to this one. (This computer is also connected via wifi, not cable.) 2. The wifi hardware in this machine is receiving, I presume, otherwise I wouldn't get the signal strength reading. (It can see other nearby networks, too. And I don't think any of them are the problem: I'm less than 3 yards from my router.) 3. The wifi hardware in this machine is transmitting: if I access the router's status pages (via 10.0.0.2) on the other machine, I can see this machine's MAC listed in the list of devices connected (there are only two, this machine and the other one), which disappears and then reappears if I manually disconnect and then (attempt to) reconnect this machine. So it seems to me, it's something at a higher level - part of XP - that's "gone peculiar"; the hardware seems to be both receiving and transmitting. Any suggestions as to how to prod it, other than rebooting? (Or ideally fix the problem, of course, but I'd live with having to do a prod.) It's very odd; if I disconnect (right-click on tray icon, View Available Wireless Networks, click on the one - which is showing Acquiring network address - and click Disconnect, then Yes), then reconnect (select the appropriate network from the list [which refreshed itself when I disconnected] and click Connect, then again on the password screen which appears]), it goes back to Acquiring ..., for ever. If I turn it back to automatic (because disconnecting told me it'd turn that off), by selecting "Change the order of preferred networks", selecting the appropriate one, Properties, Connection, Connect when ... on range (which turns it back to automatic), it does the same, i. e. sits at Acquiring ... for ever. I can't "ping" 10.0.0.2 from a command prompt, or access it from a browser. (When connected, I can.) And yet if I reboot, it'll connect fine. (It's just tedious having to do so, of course.) Samsung NC-20 netbook; "Atheros AR5007EG Wireless Network Adapter" it says, and also "This device is working properly"; "This connection uses the following items" has them all ticked. (Besides, it's been working for years.) Final thought - I see under Configure ... Advanced that "Power Save Mode" is set to Normal (the choices being Maximum, Normal, or Off); I could try turning it to Off (I use the machine on external power anyway), but (a) surely if it did power down it ought to reconnect when needed (b) why has it just started happening? Remember: o machine next this one has identical connection that works continuously o hardware is receiving (signal strength, and can see networks) o hardware is transmitting (appears in MAC list) o reboot cures all, possibly for days a puzzling one! Say, for example, DHCP was blocked. You could be "Acquiring network address" for some time, if the router won't give you an address, or the Firewall prevents it. http://www.cnet.com/forums/discussio...ddress-174797/ Signal strength excellent, but higher parts of the stack can block completion. Your job is to figure out the mechanism, and even which piece of hardware is actually doing it (could be local Firewall, could be router). The router needs a large enough DHCP pool, to hand out addresses to everyone. Even something as simple as MAC address filtering on the router, then (somehow) the MAC address value gets changed, could stop communications. Just keep building a bigger and bigger list of reasons :-) Paul |
#20
|
|||
|
|||
"Acquiring network address" - what gives?
In message , Paul
writes: [] Say, for example, DHCP was blocked. You could be "Acquiring network address" for some time, if the router won't give you an address, or the Firewall prevents it. http://www.cnet.com/forums/discussio...is-stuck-acqui ring-network-address-174797/ I thought, "I'll have a look at that" - but it's gone again! This is getting tedious. (It had stayed up some hours after last reboot.) Signal strength excellent, but higher parts of the stack can block completion. But why, after working fine for years (machine turned off during day, on when I get in from work, mostly remained fine until turned off next morning, and from Saturday evening to Monday morning if I didn't go out Sundays), but has now started this dropping out! Your job is to figure out the mechanism, and even which piece Yup, I'm trying ... of hardware is actually doing it (could be local Firewall, could be router). The router needs a large enough DHCP pool, to hand out addresses to everyone. Only local firewall is software one (Avira) in this machine, plus whatever's in the router (not any firewall I'm aware of, though I think it does do NAT). Even something as simple as MAC address filtering on the router, Whitelisting? As it happens I do have it set up that way ... then (somehow) the MAC address value gets changed, could stop .... but it seems very odd (I've never heard of it happening) that this machine's MAC could spontaneously change - actually, no, it isn't even doing that, because when I look at the MACs connected (or trying to) on the modem/router's status pages via the other machine, I can see this one appearing - and it hasn't changed. (But good call!) communications. Just keep building a bigger and bigger list of reasons :-) I'd like to be able to _start_ the list! But everything I've thought of so far, I think I've been able to rule out. Paul OK, another restart coming up, so I can have a look at that webpage you suggested (and of course send this post ...) It seems most _likely_ that some hardware has gone peculiar, since I'm not aware of having changed any software setting recently - and I could easily buy an external dongle; however, (a) no point in wasting money however little, (b) if it _isn't_ that, I'll be no better off. -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf DOS means never having to live hand-to-mouse. |
#21
|
|||
|
|||
"Acquiring network address" - what gives?
In message , "J. P. Gilliver
(John)" writes: In message , Paul writes: [] Say, for example, DHCP was blocked. You could be "Acquiring network address" for some time, if the router won't give you an address, or the Firewall prevents it. http://www.cnet.com/forums/discussio...is-stuck-acqui ring-network-address-174797/ I thought, "I'll have a look at that" - but it's gone again! This is getting tedious. (It had stayed up some hours after last reboot.) I now have looked at the page. I don't _think_ it's relevant: o it says if you disable the firewall/ICS disable your LAN enable your LAN it'll get stuck in "Acquiring". I wasn't doing any of that. o it says eventvwr.exe, System area should show an event id of 7023; I don't have any 7023 under System. o the KB it links to seems to be for XP SP2; this machine was SP3 when I bought it new. And of course o this has just (last few days) started happening. Signal strength excellent, but higher parts of the stack can block completion. But why, after working fine for years (machine turned off during day, [] could be router). The router needs a large enough DHCP pool, to hand out addresses to everyone. I haven't changed anything in the router - and the only things connected to it are this machine and the W7 machine next to it (which isn't suffering any such problem, even though it spends a lot more of its time asleep since I hardly use it - it's almost only on in case my blind friend Skypes me). [] OK, another restart coming up, so I can have a look at that webpage you suggested (and of course send this post ...) Been up about three-quarters of an hour so far, still connected ... (-: It seems most _likely_ that some hardware has gone peculiar, since I'm not aware of having changed any software setting recently - and I could easily buy an external dongle; however, (a) no point in wasting money however little, (b) if it _isn't_ that, I'll be no better off. Event Viewer|System _does_ have quite a lot of _Warning_s source "Dhcp", but no errors. (I see it has an "Export List" facility; I could send you a dump?) I'll admit most of what's in Event Viewer is above my head. -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf Tact is the ability to describe others as they see themselves. -Abraham Lincoln, 16th president of the U.S (1809-1865) |
#22
|
|||
|
|||
"Acquiring network address" - what gives?
J. P. Gilliver (John) wrote:
(snip) It seems most _likely_ that some hardware has gone peculiar, since I'm not aware of having changed any software setting recently - and I could easily buy an external dongle; however, (a) no point in wasting money however little, (b) if it _isn't_ that, I'll be no better off. Event Viewer|System _does_ have quite a lot of _Warning_s source "Dhcp", but no errors. (I see it has an "Export List" facility; I could send you a dump?) I'll admit most of what's in Event Viewer is above my head. Many laptops have an internal wifi card that plugs in (mine all did). You could try re-seating it. |
#23
|
|||
|
|||
"Acquiring network address" - what gives?
In message , Paul in Houston TX
writes: J. P. Gilliver (John) wrote: (snip) It seems most _likely_ that some hardware has gone peculiar, since I'm not aware of having changed any software setting recently - and I could easily buy an external dongle; however, (a) no point in wasting money however little, (b) if it _isn't_ that, I'll be no better off. Event Viewer|System _does_ have quite a lot of _Warning_s source "Dhcp", but no errors. (I see it has an "Export List" facility; I could send you a dump?) I'll admit most of what's in Event Viewer is above my head. Many laptops have an internal wifi card that plugs in (mine all did). You could try re-seating it. Thanks; I might indeed end up trying that. Though it being loose wouldn't explain (to me, anyway) why it appears to be working - i. e. both transmitting [it can see networks] and receiving [I can see it is there when I look at the router's status page from another computer] - but not connecting. Nor why a reboot should make it go. Nearly two hours since last reboot - still connected ... (-: -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf Thankfully, I know where the bodies are buried (the abandoned Television Centre, in the /Blue Peter/ Garden), ... - Eddie Mair, RT 2015/4/25 to 5/1 |
#24
|
|||
|
|||
"Acquiring network address" - what gives?
J. P. Gilliver (John) wrote:
In message , Paul in Houston TX writes: J. P. Gilliver (John) wrote: (snip) It seems most _likely_ that some hardware has gone peculiar, since I'm not aware of having changed any software setting recently - and I could easily buy an external dongle; however, (a) no point in wasting money however little, (b) if it _isn't_ that, I'll be no better off. Event Viewer|System _does_ have quite a lot of _Warning_s source "Dhcp", but no errors. (I see it has an "Export List" facility; I could send you a dump?) I'll admit most of what's in Event Viewer is above my head. Many laptops have an internal wifi card that plugs in (mine all did). You could try re-seating it. Thanks; I might indeed end up trying that. Though it being loose wouldn't explain (to me, anyway) why it appears to be working - i. e. both transmitting [it can see networks] and receiving [I can see it is there when I look at the router's status page from another computer] - but not connecting. Nor why a reboot should make it go. Nearly two hours since last reboot - still connected ... (-: Most of the industrial equipment we work on is plug-in modular and somewhat similar to ordinary computers, just bigger and more durable. Oxide sometimes develops on the contacts and prevents correct communication. Sometimes the tcp/ip stacks develop an oxide layer on the contacts and we can see and communicate with the stacks but the stacks can't send the serial data to the other modules, or the reverse. Sometimes they partially work. Cleaning the contacts and re-seating the parts gets them going again for a while. |
|
Thread Tools | |
Display Modes | |
|
|