Re: Lost Dialup, Lost LAN
From: Mat Brown (matbrown_at_mindspring.com)
Date: 06/24/04
- Next message: Dale Basye: "Client for Microsoft Networks"
- Previous message: anonymous_at_discussions.microsoft.com: "Re: Wireless WEP Encryption not 128-bit"
- In reply to: Fred Marshall: "Re: Lost Dialup, Lost LAN"
- Next in thread: Jeffrey Randow (MVP): "Re: Lost Dialup, Lost LAN"
- Reply: Jeffrey Randow (MVP): "Re: Lost Dialup, Lost LAN"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 24 Jun 2004 21:37:16 GMT
"Fred Marshall" <fmarshallx@remove_the_x.acm.org> wrote:
> First things first.
> Remove all instances of TCP/IP and then add that protocol back.
Tried that. Couldn't remove it from the LAN, and couldn't just delete the
LAN from the list of connections either. Doesn't seem to be any way to
really restore TCP/IP when it gets damaged in XP. They say "netsh int ip
reset" is supposed to do it, but it doesn't seem to.
> If you ping a known IP address on the LAN then there should be no reason
for
> name resolution and the ping program should say:
> Pinging 192.168.1.1 with 32 bytes of data.
That's what I had been trying, no such luck.
> If the IP address is garbled, that suggests a problem with the ping
program
> (can't be sure)...
Is there a way to restore that in XP, or is it effectively part of TCP/IP?
> When you set up ICS, you have to set up the ethernet interface to have the
> right IP address. Was this done? As I recall, it sets up a bridge and
the
> bridge takes over those functions..... If not, you may have taken the ICS
> computer off the LAN for IP purposes at least... and then you'd not be
able
> to ping it, etc.....
It actually automatically sets the LAN to the proper IP address. I did
double check it to make sure. But what I later realized was that the
computer with the problem had by then lost all communication with the LAN
anyway.
> Also, if you are really connecting the computers with NetBEUI then you may
> not be getting a clear picture of the TCP/IP situation. You can find lots
> of literature on the web suggesting that *only* TCP/IP is necessary.
Yeah, I don't know why IPX/SPX and NetBEUI were enabled on the LAN, but I've
been removing them since I noticed they were there.
> You seem to be having problems with the dialup in general. So that would
be
> a separate investigation.
Well, had both problems not started at the same time, I would be more
inclined to agree with your assessment, but it had all been working on all
the machines, then both stopped on that one, and then later same problems
started showing up on the other. All the machines in the office use not only
the same ISP, but the same phone line and dialup account. (They don't use
the internet a whole lot.) All the other machines have continued to be able
to dialup without problem. Finally, the machine where it first showed up, I
did a reformat reinstall on, and it now connects just fine again, so it
wasn't some kind of hardware problem. The second machine still connects to
LAN, but the Ping information is garbled, and while it will dialup and
connect to the internet, it doesn't communicate with it, I cannot ping
anything out there. Once again, it is looking to me like TCP/IP corruption,
but I still don't know of any way to fix that in Windows XP...
- Next message: Dale Basye: "Client for Microsoft Networks"
- Previous message: anonymous_at_discussions.microsoft.com: "Re: Wireless WEP Encryption not 128-bit"
- In reply to: Fred Marshall: "Re: Lost Dialup, Lost LAN"
- Next in thread: Jeffrey Randow (MVP): "Re: Lost Dialup, Lost LAN"
- Reply: Jeffrey Randow (MVP): "Re: Lost Dialup, Lost LAN"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
