On Mon, Apr 12, 2010 at 4:02 PM, Jay Dale <[email protected]> wrote: > Wifi is 10.0.1.0/24, Sonicwall is 10.0.1.1. DHCP range on local is between > .100 and .200, same for wifi. The IP for the server is .60 that keeps > rejecting ...
Okay, given what you've said so far, I don't think changing the IP address of the SonicWall on the wired network is likely to help anyway. If the SonicWall is mistakenly doing proxy ARP, or otherwise configured to claim an additional incorrect address, it would keep doing so. I don't know why they suggest that. (Unless the SonicWall support folks are just engaged in some "shotgun debugging": "The making of relatively undirected changes to software in the hope that a bug will be perturbed out of existence. This almost never works, and usually introduces more bugs." (Jargon File)) If you can, I'd suggest taking the server that keeps rejecting, and unplugging it from the LAN. Then use a different computer (still plugged into the LAN) to try ping'ing 192.168.0.60 and see if anything answers. If it does, you can start tracing there. :-) > ... in the Sonicwall ARP cache it is listed with the correct MAC address. ARP caches are generally overwritten as soon as a new answer comes in. Since the problem is intermittent, it could be that when the failure mode occurs, the ARP cache in the Sonicwall would show something different, but by the time you can check it, that bogus answer has been replaced. > And we only have 5 guys in this office, and I've walked around and asked - > they're all developers and are fairly knowledgeable about what I ask them > (for the most part - they are developers you know...:)) Hmmm. Well, they might not realize that combination print-server/coffee-maker they got at Staples is also a DHCP server. Or, they could just be flat-out lying. But I guess we'll take their word for it for now. :) -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
