On Tue, Oct 25, 2011 at 20:39, Michael Borthwick <span dir="ltr"><<a href="mailto:holden@netspace.net.au">holden@netspace.net.au</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I hope you'll pardon the off topic post.<br>
<br>
At a client site an on Friday a 3 year old Acer Aspire M1610 desktop<br>
running Vista was working fine and on Monday morning was unable to<br>
connect to the Internet.<br>
<br>
Specifically it does not get a lease from the cable modem router<br>
whether set to "obtain in IP address automatically" or when manually<br>
set within the range of addresses the router allocates by default<br>
(which is the entire 192.168.0.x subnet).<br>
<br></blockquote><div><br>not sure why this would be..<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I have put the PC NIC on a 10.10.0.x subnet connected to eth3 of a<br>
MicroTik RouterBOARD 532 and put eth2 of the MicroTik on the cable<br>
modem routers 192.168.0.x subnet and created a route between them. The<br>
MicroTik gets a lease but the PC still cannot connect to the Internet<br>
(it still shows up as unidentified network) although the PC can ping<br>
the router at 192.168.0.1<br></blockquote><div><br>So, you have evidently demonstrated that the pc's ethernet still works, which is one thing. Note, however, that unless you had a nat/masquerade rule in the 532 for the PC, this could have prevented proper internet access. It's not entirely clear where the route you added was, but note that even if the netgear has a route to 10.10.0.x, it may not NAT such sources out to the internet.<br>
<br>If I'm right, perhaps knowing exactly what happened in this test will help you isolate the real problem.<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I have reset the cable modem router to factory defaults in case it has<br>
stored some kind of exception to the MAC of the PC even though I was<br>
cloaking this behind the RouterBOARD<br></blockquote><div><br>As above, it may have been a different issue at that point. <br></div><div> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Whirlpool says that the Netgear CGD24N is a bjorked device especially<br>
for a small business (there are around a dozen wired clients on a<br>
Cisco switch) and up to half-a-dozen iOS devices at various times. It<br>
does need to be reset a lot - however after a return to factory<br>
defaults it is hard to believe it can be fault and all other wired and<br>
wireless devices are OK, at least for the time being.<br></blockquote><div><br>I'm guessing it's a windows problem rather than with the router, especially if other devices are working fine. Can't really be more specific than that, though<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
I've exhausted my trouble-shooting abilities - particularly on the<br>
Windows side. Is there some other layer in the Windows OS that could<br>
be holding it down ? I really don't know where else to look or what to<br>
try.<br>
At this stage I'm considering.<br>
1. Buyng a new NIC even though the built in one seems fine from a<br>
hardware POV to see if the "unblocks" it.<br>
2. Reinstall Vista from the backup image on the HD.<br></blockquote><div><br>Boot something else from a livecd and verify the hardware, to start with. Then at least you have confirmed a software issue on the PC. That could be anything from bad/accidental config to malware.<br>
</div></div><br>-- <br>Dan.<br>