I thought the Red device would be perfect for a small new remote site we have, but I am flummoxed. I wanted an easy plug & play setup, without having to reconfigure the new site's network, so the transparent/split mode looked perfect.
The intention is to put the device between the router and the switch at the remote site. I configured the device here, and tried it out behind a router in a NAT'd address space. It worked fine. So, I sent it off.
It turns out that at the remote site, DHCP is turned off at the router, and handled instead by a Windows domain controller. So, the Red device wouldn't connect between the router and the switch. No DHCP on the WAN side. So, in the Red configuration, I put in a free local IP address (192.168.1.2) on the remote network. It still won't connect. It WILL connect, however, when WAN1 is connected to the switch segment with the DHCP server.
Does anybody have any ideas? Am I out of luck, or should there be a way to make this work? I called support, and they said the static IP setting only works with public IP addresses in transparent mode. That sounds a little weird to me. They want me to turn on DHCP at the router.
Another thing I thought of after the remote site went home (they are in the UK) was the IP settings on the interface page. Dynamic IP is set there. Should I change this to static? If so, what IP should I put in there? The same one I configured on the Red page, or a different one?
Thank You!
This thread was automatically locked due to age.
