Re: flaky DHCP
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Wed, 26 Apr 2006 18:25:58 -0500
However, when I replace the Linksys router with an SMC router I'm not
getting a good DHCP address. How do I figure out why not?
Does the router separate the DHCP clients from their
server?
If so, then most likely you need to make the setting on
the router that is equivalent to "DHCP Relay" (aka
"IP Helper address" by Cisco, IIRC) or "Bootp
forwarding."
The clients BROADCAST must either be relayed
or forwarded to the DHCP server if they are not on the
same "broadcast domain" (i.e., a router separates them.)
<hawat.thufir@xxxxxxxxx> wrote in message
news:1146087064.906837.163010@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Here I'm connecting to a linksys 802.11g router with an Asus WL-330g
802.11g wireless NIC adapter:
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-1999 Microsoft Corp.
C:\>ipconfig /all
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : geidiprime
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : vc.shawcable.net
Ethernet adapter 3com:
Connection-specific DNS Suffix . : vc.shawcable.net
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100
PCI TX NIC
(3C905B-TX)
Physical Address. . . . . . . . . : 00-10-4B-70-F1-87
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 64.59.144.92
64.59.144.93
Lease Obtained. . . . . . . . . . : Thursday, April 20, 2006
10:20:17 AM
Lease Expires . . . . . . . . . . : Friday, April 21, 2006
10:20:17 AM
C:\>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<10ms TTL=64
Reply from 192.168.1.1: bytes=32 time<10ms TTL=64
Reply from 192.168.1.1: bytes=32 time<10ms TTL=64
Reply from 192.168.1.1: bytes=32 time<10ms TTL=64
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\>ping www.google.com
Pinging www.l.google.com [66.102.7.147] with 32 bytes of data:
Reply from 66.102.7.147: bytes=32 time=40ms TTL=245
Reply from 66.102.7.147: bytes=32 time=40ms TTL=245
Reply from 66.102.7.147: bytes=32 time=60ms TTL=245
Reply from 66.102.7.147: bytes=32 time=40ms TTL=245
Ping statistics for 66.102.7.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 60ms, Average = 45ms
C:\>
C:\>
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
.
- References:
- flaky DHCP
- From: hawat . thufir
- flaky DHCP
- Prev by Date: flaky DHCP
- Next by Date: Re: DHCP Inside / Outside
- Previous by thread: flaky DHCP
- Index(es):
Relevant Pages
|