I know someone with a company laptop on a dhcp office lan, who upgraded the
laptop from 98 to win2k. Once the upgrade was done, the laptop could not be
made to work via dhcp, but did work with statically mapped ip parameters.
Are you using dhcp??
Bri
- Original Message -
From: "
Date: Saturday, June 23, 2001 01:24:54 AM=0D
To: George Murphy CCNP; [EMAIL PROTECTED]=0D
Subject: Re: Got A Side Job and am baffled by one client.. [7:9612]=0D
=0D
I know someone with a company laptop on a dhcp office lan, who upgraded t=
he=0D
laptop from 98 to win2k. Once the upgrade was done
On Sat, 23 Jun 2001, George Murphy CCNP wrote:
> I snagged a side job (pays great) and am wondering about a situation. Ok.=
> =2E. here goes. One PC out of about 15 that work great can see Server res=
> ources but cannot browse the web or ping outside. They are using an NT 2k=
> Server, 2900XL
as you suggested.
Chuck
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
[EMAIL PROTECTED]
Sent: Saturday, June 23, 2001 12:10 AM
To: [EMAIL PROTECTED]
Subject: Re: Got A Side Job and am baffled by one client...... [7:9612]
On Sat, 23 Ju
George,
I think you just answered your own question. IMHO, if the other PC's have
the sameconfig and are able to get an address, it is most likely a SID that
is gotten corrupt on the box in question. I would back up data, rebuild,
and
readd it to the workgroup.
My .02c,
BTW, if you want to blo
have you tried changing the hostname whilst the pc is in a workgroup and
then rejoin the domain with a new hostname ?
- Original Message -
From: "George Murphy CCNP"
To:
Sent: Saturday, June 23, 2001 7:30 AM
Subject: Got A Side Job and am baffled by one client.. [7:9612]
> =0D
> He
I had a similar problem with my home network lab.
I have both NT4 /W2k servers. (as well as NT4, W2K, W9* workstations)
The first big problem was that I could log in from one machine but not
another.
It turned out that W2K played with the auto duplex on the card. It seemed
that after every boo
Do it by the layers.
1. Check nic, cable, and other physical layer (1) issues.
2. Check layer 2 ( arp, mac, etc)
3. Check layer 3 (ping IP address , not host name, start with self, then
local workstation, then server, etc). Ping local router, than ISP router.
Once that is done, then try ping
Shot in the dark: I read something in a M$ publication today that a
WinModem not on the HCL can cause serious networking problems. I have yet
to validate this, but your problem is goofy. I would have guessed NAT
overloading as well. There's always the "proper" way to repair M$
problems... Form
am baffled by one client..
[7:9612]
George,
I think you just answered your own question. IMHO, if the other PC's have
the sameconfig and are able to get an address, it is most likely a SID that
is gotten corrupt on the box in question. I would back up data, rebuild,
and
readd it t
A Side Job and am baffled by one client.. [7:9612]
Shot in the dark: I read something in a M$ publication today that a
WinModem not on the HCL can cause serious networking problems. I have yet
to validate this, but your problem is goofy. I would have guessed NAT
overloading as well. There
11 matches
Mail list logo