Sudden wireless network problem

On 14 Aug 2005 19:58, "Bobby" <(E-Mail Removed)> wrote:

>> Dangerously, if a past restore point was infected, 'going back' to solve
>> a problem might introduce a trojan/virus to the system, once more
>
> Also dangerously, throwing your PC out of an upstairs window might cause
> your hard drive to malfunction.

It could be a worse outcome for your relative who happened to be underneath
it when you decided to throw it. The difference is that throwing a PC from
any window is clearly expected to cause significant problems, while getting
the system to restore a past 'working' snapshot would be expected to assist
with a problem, not cause more. Silly suggestion to make about throwing PC
if there's meant to be any form of parallel between these two situations!

--

UK ADSL <http://tinyurl.com/5jpa4> - Happy to save cash with Plus.Net!!
E-mail + files - 30 day free trial - <http://web.vfm-deals.com/runbox/>
USENET news service? <http://tinyurl.com/3rjw4> (plans from under US$5)

In an earlier contribution to this discussion,
Bobby <(E-Mail Removed)> wrote:

>> Dangerously, if a past restore point was
>> infected, 'going back' to 'solve' a problem might introduce a
>> trojan/virus to
>> the system, once more
>
> Also dangerously, throwing your PC out of an upstairs window might
> cause your hard drive to malfunction.

You mean it will make a dent in the tarmac? <g>
--
Cheers,
Tim
______
Please reply to newsgroup. Reply address is invalid.

Bobby wrote:
> Also dangerously, throwing your PC out of an upstairs window might cause
> your hard drive to malfunction.

It might also land on the courier coming to leave you a card telling you
you're not in.

Owain

"Bobby" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>> It solves nothing in my experience, but that could be because I
>> always disable it
>
> Yes, that might be the reason.
>
> Disabling system restore IMO is not a good idea. It solves 99% of software
> problems.

And, even if you cant get windows up and running, you can use the restore
settings to recover your previous backed up registry.

If you have system restore switched off, unless you manually backup your
registry, and your registry files get corrupted, then your installation is
unrecoverable.

Gaz

"poster" <us-(E-Mail Removed)> wrote in message
news:(E-Mail Removed). net...
> On 14 Aug 2005 18:11, Rob Morley <(E-Mail Removed)> wrote:
> ...
>
>>> Disabling system restore IMO is not a good idea. It solves 99% of
>>> software
>>> problems.
>
>>Why did you snip the bit that said "I always disable it because of
>>the problems that it has caused me in the past"?
>
>
> To have the last word, perhaps thinking that a couple of posts about
> problems
> when system restore is used will be ignored if 'solves it in 99% of cases'
> is
> the last thing people see on Google in a year's time. FWIW, I don't have
> any
> System Restore in use, and in many cases it needs to be disabled when
> someone
> has had a virus problem, so the benefits of using it get lost quickly when
> it
> is (probably) seen as being useful. Dangerously, if a past restore point
> was
> infected, 'going back' to 'solve' a problem might introduce a trojan/virus
> to
> the system, once more :-( We lived without it in the past, didn't we :-)

but you can repair your registry from your system restore folder.......

Not as simple as scanreg /restore (i dont understand why MS did this....)
but it does work.

erd commander is excellent at accessing full system restore functionality as
well....

Gaz

> --
>
> E-mail + files - 30 day free trial - <http://web.vfm-deals.com/runbox/>
> Can be added as an MX record, so your domain mail gets stored safely,
> with IMAP / POP / SMTP (not locked to port 25) facilities.
>
> USENET news service ? <http://tinyurl.com/3rjw4> (plans from under US$5)

Bobby wrote:
> Thanks for the suggestions.
>
> The problem PC is a desktop system (not a laptop).
>
> The network also includes two laptops (including the one I'm typing
> this on) and another desktop PC. All connect wirelessly. All work
> perfectly.
> My problem PC was working perfectly. I did not make any network
> changes. I am reluctant to stop messing about with TCP/IP settings.
>
> My modem and router is a combined unit. I switched it off last night
> but the problem persisted this morning when I tried again. I presume
> switching it off is the same as a reboot. The lights on the
> modem/router report no problems whatsoever and every other PC/laptop
> works OK.
> I can't connect to my modem/router web management page so something
> fundamental must be going wrong between my PC and the router.
>
> I am going to try to re-install my wireless network adaptor software.
> Then I will replace my wireless adaptor to see if that helps.
>
> Bobby
>
> "Rick "Nutcase" Rogers" <(E-Mail Removed)> wrote in message
> news:eooUnM$(E-Mail Removed)...
>> Hi Bobby,
>>
>> Reset the router first. Shut down the router and broadband modem.
>> Then power up the modem and wait until it makes its connection, then
>> power up the router. You may also find that you need to restart the
>> systems connected to it, but you may get around it by running
>> ipconfig /release, then /renew from a cmd prompt.
>>
>> --
>> Best of Luck,
>>
>> Rick Rogers, aka "Nutcase" - Microsoft MVP
>> http://mvp.support.microsoft.com/
>> Associate Expert - WindowsXP Expert Zone
>> www.microsoft.com/windowsxp/expertzone
>> Windows help - www.rickrogers.org
>>
>> "Bobby" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> My home wireless network has worked flawlessly for months but one
>>> of my PCs suddenly refused to work last night.
>>>
>>> I have a BT Broadband connection (1Mb). This connection works OK
>>> since the other PCs in my home connect OK (I am typing this from my
>>> wireless laptop).
>>>
>>> My hardware is: BT Voyager wireless router/modem. Belkin wireless
>>> network adapter. All running at 801g (54Mbit). I let my Belkin
>>> software manage the connection (not Windows). I'm running Windows
>>> XP SP2. Last night my Internet connection suddently went down. The
>>> PC was
>>> previously working fine (and connecting to the Internet without a
>>> problem). The icon in the system tray was reporting "limited
>>> connectivity" but I had something else to do and ignored the
>>> problem. But this morning the same problem arose. This time I
>>> appeared to
>>> have full (90%) connectivity according to the icon in the system
>>> tray. So I expected to connect to the Net without problems - but I
>>> couldn't (it timed-out). Worse, I can't connect to my router's home
>>> page. But my PC reports that my wireless adaptor is working OK and
>>> that I have connectivity (ranging from 90-95%). But nothing works.
>>>
>>> Sometimes the system tray reports "limited connectivity" but if I
>>> disable and enable the connection it goes back to (almost) full
>>> connectivity. But I still can't "see" my wireless router (i.e. it's
>>> admin web page). I'm at a loss. Help!
>>>
>>> Cheers.
>>>
>>> Bobby

Assuming that the problem PC runs XP, download a copy (Google) of
winsockxpfix.exe and lspfix.exe. Run both (although winsockxpfix seems
to do the work of both) to repair layered services that can become
corrupted for no apparent reason that I have been able to ascertain.
The corruption leads to exactly the type of problem you describe.

Q

In an earlier contribution to this discussion,
Quaoar <(E-Mail Removed)> wrote:

>
> Assuming that the problem PC runs XP, download a copy (Google) of
> winsockxpfix.exe and lspfix.exe. Run both (although winsockxpfix
> seems to do the work of both) to repair layered services that can
> become corrupted for no apparent reason that I have been able to
> ascertain. The corruption leads to exactly the type of problem you
> describe.
>
Is it likely to fix a problem which I have with my laptop?

The laptop normally connects to the internet via my router, using its
ethernet connection - no problem. However, if I am away from home, I use it
to dial into the internet, using it's built-in modem. The problem is this:

If I dial in and then disconnect, I cannot connect again without re-booting.
Actually, that's not strictly true. I can *connect* to an ISP but I can't
actually *do* anything. If I look at the config in ipconfig /all, it's
apparent that it's left behind a stray PPP record which I can't get rid of
without re-booting - and although dialling in again creates a new one, it
doesn't pick up the gateway and DNS addresses properly. I've tried all the
ipconfig options (dnsflush, etc.) but nothing works.

Anyone got any ideas?
--
Cheers,
Tim
______
Please reply to newsgroup. Reply address is invalid.

Tiscali Tim wrote:
> In an earlier contribution to this discussion,
> Quaoar <(E-Mail Removed)> wrote:
>
>>
>> Assuming that the problem PC runs XP, download a copy (Google) of
>> winsockxpfix.exe and lspfix.exe. Run both (although winsockxpfix
>> seems to do the work of both) to repair layered services that can
>> become corrupted for no apparent reason that I have been able to
>> ascertain. The corruption leads to exactly the type of problem you
>> describe.
>>
> Is it likely to fix a problem which I have with my laptop?
>
> The laptop normally connects to the internet via my router, using its
> ethernet connection - no problem. However, if I am away from home, I
> use it to dial into the internet, using it's built-in modem. The
> problem is this:
>
> If I dial in and then disconnect, I cannot connect again without
> re-booting. Actually, that's not strictly true. I can *connect* to an
> ISP but I can't actually *do* anything. If I look at the config in
> ipconfig /all, it's apparent that it's left behind a stray PPP record
> which I can't get rid of without re-booting - and although dialling
> in again creates a new one, it doesn't pick up the gateway and DNS
> addresses properly. I've tried all the ipconfig options (dnsflush,
> etc.) but nothing works.
>
> Anyone got any ideas?

Give winsockxpfix.exe a try for this. It is essentially harmless, IMO,
based on the lack of negative comments on its use.

Q