| reply to mmacedon
Re: [Help Me] DWL-G710 "IP address conflict" Question Thanks again for all of your help. There were no bridged connections in the laptop.
I hate to admit it, but I have abandoned the repeater idea. Based on what I've been reading in many of these boards, increasing the range of my network may be more effectively done by getting a directional, higher gain antenna for my original router.
I got a hawking tech 15dbi corner antenna for my router and that fixed the weak coverage problem in the basement. Of course, this also didn't come with the associated IP conflict and reduced throughput problems of the repeater. Anyway, all is well now (although I hated giving up on the networking problem I couldn't understand). Thanks again for all of your help.
-Mike |
|
 funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5 | OH NO! I'm disappointed!
Actually I'm glad for you. I just wish I could figure out what was causing all of that ruckus!
Congrats! Yes, the directional antenna is a better choice for so many reasons! |
|
| reply to mmacedon
Re: [Help Me] DWL-G710 "IP address conflict" Quest I've had exactly the same problem, but with a DI-624 AP and
a DWL-G800AP in repeater mode. Additional information:
o if my wireless devices (i.e. laptop) is close to the repeater, and clearly using it, no problems occur.
o if my wireless devices are between the repeater and the DI-624 -- problems.
I *think* I've finally worked around the problem by turning OFF the DI-624 DHCP server, altogether, and assigning static IP addresses to all of my machines. DLink support was marginally helpful, but mostly just recommended upgrading firmware.
This is not pretty, and a pain when a laptop is mobile, but it seems to work (at least today).
George |
|
| For what it's worth, turning off the DHCP server on the
router didn't help anything. I'm still having the
problem. |
|
funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5
1 edit | said by gmfeinberg :
For what it's worth, turning off the DHCP server on the
router didn't help anything. I'm still having the
problem.
Try these suggestions:
To work around it, make sure you disconnect from the previous connection path, then reconnect to the same device. This clears the ARP cache.
You can also do the command ...
ARP -d *
... as another workaround. --
Robb Topolski -= funchords.com =- Hillsboro, Oregon USA
~ Keeper of the D-Link FAQ ~ Did you Search? ~ More features, Free! Join BBR! ~ |
|
| I've found a solution.
The conflict is occuring as a result of a Windows machine
trying to detect possible IP address conflicts using
what's called a "Gratuitous ARP." This is usually a
fine thing to do, but...
There are 2 problems here:
1. The fact that the repeater is answering the
Windows "Gratuitous ARP" using its own MAC address.
2. The "Gratuitous ARP" itself, which is sent by the TCP/IP
stack in Windows to detect conflicting IP addresses.
I cannot control or fix (1), but (2) can be "fixed" by
turning off the ARP. If you search the net for "disable
gratuitous arp" you'll find a bunch of Microsoft knowledge
base references to a registry setting in the tcpip parameters called "ArpRetryCount"
The specific registry key is:
HKEY_LOCAL_MACHINE->SYSTEM->CurrentControlSet->Services->Tcpip->Parameters->ArpRetryCount
The articles also imply that this setting does not
apply to Windows XP, and you will not find that key
in your registry, either. However, it does apply.
You just need to add it as a new DWORD key, with
the value set to 0.
Note that this is a semi-dangerous thing to do if you
spend a lot of time on open wireless networks, because
IP address conflicts can happen, and are bad. But for
a controlled, home network, it's safe.
George |
|
funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5 | Wow!!!!!!!!
Thanks!!
I'm so glad you let me know ... and congrats on finding it! |
|
| If anyone is interested I am having this same problem... I got fed up with firmware upgrades and downgrades and configuration and I finally came to the conclusion that it was an ARP problem like all of you did. I was so sick of it I came up with the following workaround:
1. Create a batch file that fixes the ARP problem with static ARP
fixarp.bat
##########
@echo off
arp -d *
arp -s 10.10.10.1 00-0f-3d-06-81-a9 REM Replace with your ROUTER MAC ADDRESS
2. (Optional) Create a batch file that checks arp status
checkarp.bat
############
arp -a
pause
3. Save these files on the desktop for easy access. |
|
funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5 | arp -d * will do it. The router will be found via an arp "WHO HAS" request broadcast. |
|
