On Mon, Apr 12, 2010 at 2:10 PM, Jay Dale <[email protected]> wrote: > There are no proxy arp's taking place because it's only one network.
You've said multiple times now there are multiple IP networks. Your "wifi" network still counts as another IP network. :) Proxy ARP, by definition, is when a gateway responds to an ARP request on one IP network on behalf of a host on another IP network. If, for whatever reason, your SonicWall is performing proxy ARP, that would cause the symptoms you are describing. Obviously the SonicWall shouldn't be doing that, but if everything was working right we wouldn't be having this conversation. :) I'm not saying this *is* the problem, but it's a possibility. > ... they're suggesting changing the LAN IP address to something different ... Do they mean renumbering your entire wired LAN, or just changing the one server's IP address? Actually, either one isn't a good solution. The right thing to do is to identify the problem device and/or configuration. What are the routers, network numbers, and netmasks involved? What does the routing table on the SonicWall look like? An example respond might be: UTP network: 192.168.1.0/24 Wifi network: 192.168.2.0/24 ISP network: 203.0.113.0/24 SonicWall is 192.168.1.1 on UTP SonicWall is 192.168.2.1 on wifi SonicWall is 203.0.113.42 on ISP ISP router is 203.0.113.1 SonicWall routing table: 192.168.1.0/24 via 192.168.1.1 192.168.2.0/24 via 192.168.2.1 203.0.113.0/24 via 203.0.113.42 0.0.0.0/0 via 203.0.113.1 -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
