Re: Weird problem
From: Steven L Umbach (n9rou_at_n0-spam-for-me-comcast.net)
Date: 07/10/04
- Previous message: mosquito_hippy: "Re: Weird problem"
- In reply to: mosquito_hippy: "Re: Weird problem"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 10 Jul 2004 20:11:30 GMT
Can you ping the dhcp server by name or IP address and can it ping you after you
assign it a static IP address for testing? I would also try running netdiag on it
looking for any failed tests that may be helpful in determining the problem. Netdiag
is one of the free support tools on the install disk in the package in the support/
tools folder. Verify that the built in ICF firewall is disabled. Try setting the
network speed of the network adapter to 100 instead of auto in it's properties if
possible and disable any settings that allow the nic to go into sleep mode in it's
properties or via XP Power Management or even in the computer cmos settings. It
certainly would not hurt to try resetting tcp/ip with the netsh command. I usually
try rebooting into safemode with networking also when trying to troubleshoot network
problems as that will bypass startup application and leave only bare minimum services
running. If possible also try connecting that computer to the same cable/port of a
functioning. Putting in another nic would be an appropriate thing to try if nothing
else seems to help. I guess as a last resort you could configure the computer with
static IP info. --- Steve
"mosquito_hippy" <mosquitohippy@discussions.microsoft.com> wrote in message
news:CD909878-C539-43A4-AB29-9606D7016D7A@microsoft.com...
> Thanks Steve, so it is a hardware problem?, a cable related problem?
>
> "Steven L Umbach" wrote:
>
> > See the link below on how to reset tci/ip in XP using the netsh command as in "
netsh
> > int ip reset resetlog.txt ". That will not however fix problems with winsock
> > corruption which can be remedied manually or with the free LSPfix utility
commonly
> > found on the internet. Usually a problem with receiving an APIPA address
> > [169.254.xxx.xxx] is a network connectivity issue. --- Steve
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;299357
> >
> > "mosquito_hippy" <mosquitohippy@discussions.microsoft.com> wrote in message
> > news:EA0104C4-1D5E-44A0-8232-944E24948A8D@microsoft.com...
> > > May be you are right, the cable thery doesn't explain why the problem is solved
> > after perform a system restore.
> > >
> > > How can i reinstall the TCP/IP stack in windows XP?
> > >
> > >
> > > "mosquito_hippy" wrote:
> > >
> > > > I manage (like how it sound) W2003 network with all WXP Pro clients but our
> > clients don't sign in the domain instead they sign in locally with in their own
pc's
> > when they need access some data from the server then they log in.
> > > >
> > > > I have a problem with one PC just one, this PC lost its IP address aleatory
> > randomly acquiring the XP's default ip address.
> > > >
> > > > My only way to sort this thing out is to restore the PC's system to a previus
> > ststus.
> > > >
> > > > My guest it is some bug (spyware, virus, etc.) messing with me.
> > > >
> > > > Any ideas.
> >
> >
> >
- Previous message: mosquito_hippy: "Re: Weird problem"
- In reply to: mosquito_hippy: "Re: Weird problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|