I am looking for some help here for my lab setup:
I have configured the UC320 and network as follows:
Windows SBS2003 serving DHCP:
IP 192.168.1.2
GW 192.168.1.1
DNS 192.168.1.2 (with forwarders setup to 4.2.2.2, etc)
DHCP Serves 192.68.1.x subnet for LAN
Actiontec Router (Verizon FiOS broadband)
LAN IP 192.168.1.1 (ethernet port 1)
Subnet 255.255.255.0
NO DHCP
VLAN 4 (ethernet port 4)
192.168.2.1
Subnet 255.255.255.252
NO DHCP
Topology #3 (Voice only, external DHCP)
LAN IP 192.168.1.6
LAN GW 192.168.1.1
SUBNET 255.255.255.0
LAN DNS 192.168.1.2
Voice (left as default 10.1.x.x subnet
WAN IP 192.168.2.2
WAN GW 192.168.2.1
WAN SN 255.255.255.252
WAN DNS 4.2.2.2
The UC320 WAN port is plugged into physical PORT #4 of the Actiontec and that port is assigned the VLAN4. THe UC320 LAN port is plugged into a switch that ties the rest of the LAN together (a few printers, the SBS server and a few workstations.
The UC320 is able to see the WAN and INTERNET and was able to download the 2.0.13 update. I can access the UC320 from the LAN. I have NO PSTN lines or SIP trunks installed on the device (though 3 PSTN trunks are enables in the config). I have NO IP handsets plugged into the network.
Every 20 minutes or so the LAN stops functioning until the UC320 WAN port is disconnected. That is, none of the machines on the LAN are able to route local or remote traffic. The second that WAN port is unplugged, functionality is restored.
IMPORTANT
If the WAN port is NOT plugged in, the same network lockup occurs, but unplugging the LAN port from the UC320 immediatly fixes the problem.
Does anybody have any clue as to what is going on?
There are no IP conflicts on the network, the LAN address of the UC320 is NOT in the DHCP pool. This behavior also existed in 2.0.6 and 2.0.9
