Re: DHCP problem on workgroup
- From: "Tanu Mutreja [MSFT]" <tmutrej@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 19 Apr 2005 20:50:25 +0530
Inline...
"briandco" <briandco@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E623E815-ACAB-4FA8-BFC9-27A1F373F457@xxxxxxxxxxxxxxxx
>
>
> "Tanu Mutreja [MSFT]" wrote:
>
>> My quick guess is that your system is unable to access the DHCP Server.
> That seems right
>>
>> "briandco" <briandco@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:7368B263-E693-4EB6-8AFA-30054E702A29@xxxxxxxxxxxxxxxx
>> > I'm having problems with a laptop that I'm trying to add to an existing
>> > workgroup based wireless network. I cannot get the laptop to see the
>> > other
>> > machines on the workgroup, or the internet. Other machines on the
>> > network
>> > cannot see the laptop and I cannot ping it.
>> > 4 machines are visible to each other on the network and have a similar
>> > IP
>> > range and the same subnet mask (255.255.255.0), but the laptop has a
>> > very
>> > different IP address and the subnet mask is 255.255.0.0).
>>
>> What's the IP address that you get? Is this something like 169.x.x.x?
> yes - its 169.254.x.xx
It's AutoNet IP Address, which gets assigned to a network card if the card
to configured to get dynamic IP address and DHCP Server is not accessible
for some reason.
> subnet mask is 255.255.0.0
> default gateway shows as 0.0.0.0 (other machines all show the IP address
> of
> the wireless gateway as the default gateway)
>>
>> > I assume the DHCP server is the Wireless Gateway (Zoom IG-4165).
>> > I have tried to manually assign the IP address when joining the
>> > wireless
>> > network
>> Not sure if I understood this correctly. What address did you assign
>> manually? Did that work, I mean in static mode were you able to ping
>> other
>> systems?
> I used the zoom connection manager to set the IP etc manually; this
> appeared
> to force a different IP address and subnet mask and default gateway on to
> the
> problem laptop but still didn't allow me to connect to the workgroup; I
> then
> reverted to DHCP hoping that would force a new DHCP lease but it just
> reverts
> to 169.254.x.xx
So, you can simply ignore 169.x.x.x address while trying to resolve this
problem. This address won't help.
Can you try to set static IP address for this Network Connection? Use a
static IP in the same range as other systems(having no issues with network
connectivity) in your network are having. Use the same subnet mask and same
default gateway as well. Then see if you get proper network connectivity. If
not then it's a different network issue than DHCP.
>>
>> > to force the change of IP address lease, and then revert to DHCP,
>> > but when I rejoin the wirless network profile it just reverts to the
>> > old
>> > IP
>> > address.
>> > I have tried ipconfig /renew and this doesn't work either - any
>> > thoughts?
>>
>> Would you please provide some more information about your network
>> configuration?
> All machines are Win2K; I'm using a Zoom Wireless Gateway, with 2 PCs on
> Zoom NICs, 1 on a Belkin NIC, 1 connected by ethernet cable to the gateway
> and the problem laptop using a Zoom PCMCIA NIC; the laptop can see the
> gateway (ie there is a good signal and its passing WEP security etc) but
> can't see the workgroup or connect to the internet. If I browse with My
> Network Places it sees the Workgroup name but only the laptop itself on
> the
> list of PCs
>>
>> -Tanu Mutreja [MSFT]
> thanks
> bc
.
- Follow-Ups:
- Re: DHCP problem on workgroup
- From: briandco
- Re: DHCP problem on workgroup
- References:
- DHCP problem on workgroup
- From: briandco
- Re: DHCP problem on workgroup
- From: Tanu Mutreja [MSFT]
- Re: DHCP problem on workgroup
- From: briandco
- DHCP problem on workgroup
- Prev by Date: Re: Map network drive in background
- Next by Date: DHCP Strange
- Previous by thread: Re: DHCP problem on workgroup
- Next by thread: Re: DHCP problem on workgroup
- Index(es):
Relevant Pages
|
