MrWu Posted July 26, 2018 Posted July 26, 2018 yesterday Hi all im not sure whether it’s the recommended way of doing this but I have 2 PCs running AIrvision software 3.9.7 these PC (well mini servers) have dual NICs so one connects to my main LAN and the other again the main LAN but on a different subnet. Both Servers are on Windows AD. So the 10.18.96.x is where I access Airvision web console and some cameras are on 200.10.0.x... I have a few cameras that are on the 10.18.96.x address and I would like to migrate them to the other subnet. please note it’s not segregated VLAN for now I haven’t got round to doing this yet. now I put 4 x G3 that are new with 200.10.0.x IP address and Airvision adopted them perfectly .. gaining confidence I tried to migrate an existing G3 to 200.10.0.x from 10.18.96.x address and it won’t adopt but stuck on status : managing ... i tried.. reseting G3 back to factory - no joy maually adding the server IP address directly on the G3 - no joy maually adding adoption token on the G3 - no joy it does seem to be a subnet problem because if I revert this old G3 back to original subnet it gets adopted no issues.. whats driving me mad is how come I setup 4 new G3 cameras with 200.10.0.x address and it has been adopted fine and managed and recording with Airvision on 10.18.96.x perfectly fine or weeks? any ideas? thanks!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now