Re: can't get connected if....

tried but got an error message"unable to contactyour DHCP server"
Thanks anyway
Ch'nG

On Sat, 29 Oct 2005 12:16:22 -0700, Jeff Liebermann
<jeffl@xxxxxxxxxxxxxxxxxxxxxx> wrote:

>On Sat, 29 Oct 2005 14:08:38 GMT, Duane Arnold <notme@xxxxxxxxx>
>wrote:
>
>>chnghs@xxxxxxxxx wrote in news:88l6m1htac25k2cdk4ubg2tg288nrng9q3@
>>4ax.com:
>>
>>> hi,
>>> got a problem which i do not know whether is usual or not.
>>> I cannot get connected to the net after i have booted up to windows
>>> then switched on my router.The status on the router shows connected
>>> but can't get to surf.
>>> Can get connected only if i have switched on the router first than
>>> boot up to windows.
>>> Is that normal?
>>> Please advise and thanks
>>> Using windows xp with a DLink router.
>>> ChnG
>
>>The router stays on 24/7 365 and you turn it off when you go on vacation.
>>The router is not like you're turning a TV on and off. Do you see an on/
>>off switch on the router? You keep switching it on and off like that and
>>it may eventually go defective on you.
>>
>>You don't turn the router off and your problem is sloved.
>
>Yep. However, try this experiment to see what's happening. Boot your
>computer first and then turn on your unspecified model DLink router.
>This is the wrong order and sequence but I'm trying to create the "no
>surf" problem. You should NOT be able to surf if things are screwed
>up the way you describe.
>
>Now, open a DOS window with:
> Start -> Run -> cmd <enter>
>and run:
> ipconfig
>
>If ipconfig says your IP address is:
> 169.254.xxx.xxx
>then DHCP did not assign an IP address to your computer. This is my
>guess as to the cause of the problem.
>
>If ipconfig says your IP address is:
> 0.0.0.0
>wait a while. It's busy trying to assign an IP address.
>
>If it says your IP address is:
> 192.168.0.xxx
>then your router is working and DHCP has assigned you a proper IP
>address.
>
>Now, run:
> ipconfig /release
> wait about 10 seconds
> ipconfig /renew
> wait about 10 seconds
> ipconfig
>
>If ipconfig now says your IP address is 192.168.0.xxx, then you just
>"fixed" the problem by forcing the router to renew the DHCP assigned
>IP address. You can do this safely without requiring that you reboot
>your computer to get things working. You should be able to surf the
>internet at this point.

.

Relevant Pages

  • Re: cant get connected if....
    ... >> then switched on my router.The status on the router shows connected ... >> but can't get to surf. ... >off switch on the router? ... If ipconfig says your IP address is: ...
    (alt.internet.wireless)
  • Re: cant get connected if....
    ... >>>You don't turn the router off and your problem is sloved. ... You should NOT be able to surf if things are screwed ... >>If ipconfig says your IP address is: ... >>then DHCP did not assign an IP address to your computer. ...
    (alt.internet.wireless)
  • Re: IP Address Help
    ... Use ipconfig /all to see all the address. ... computer and router have an IP address and you have DHCP ... | that this is slowing down my cable internet connection ...
    (microsoft.public.windowsxp.general)
  • Re: DHCP on SBS 2003 - BAD_ADDRESS in DHCP lease list
    ... If you look in DHCP Server to see what has that addreess ... you could also go to each workstation and do an ipconfig /release all to clear old leases and then do an ipconfig /renew ... I set the scope to 192.168.0.110 to 220, where the router had it 100 to ... This was done to rectify the issue with the server being locked at 100 ...
    (microsoft.public.windows.server.sbs)
  • Re: No IP on boot with Netgear and XP
    ... The router and PC are in the same room. ... The 169 IP being assigned means the O/S could not get an IP from the DHCP ... server on the router and it timed out with the O/S assigning the 169 IP. ... IPconfig /renew at the DOS Command Prompt to see if an IP can be assigned ...
    (alt.internet.wireless)