silvestre

Easiest fix is an in place upgrade which will fix the corruption as someone mentioned above. Other than that you need to check the cbs.log.

Did you update MDT and ADK?

https://community.spiceworks.com/how_to/116865-add-drivers-to-mdt-all-versions-total-control-method

Add the Ethernet drivers to the boot image for that particular model

What did you try? Did you add drivers ? Where did you add the drivers ?

From the error it looks like you need to add your network drivers form the new pc in your boot image

np , i hope you find the solution

needs further diagnosing, without access im afraid will be very difficult.

Hi remove the trafic filters first and redeploy if you can access everything. Once you get it working with it being fully open to the subnet you can then make further changes.

paste your xml again

if the route is not showing then yes there is an issue with your xml

how are you deploying the profile?

single nic is supported with rras. try with route 10.0.0.0/8 to include your entire range and redeploy the profile. you can check with powershell on the client to show route if the route is added. You do not need to deploy a User tunnel unless you plan on using NRPT.

you will also need the DNS servers used on th e VPN server added to the route in DT.

you have one route specified and that too its incorrect. 10.42.92.0/32 (10.42.92.0 is not a valid IP . With a /32 subnet you need to provide an actual ip for example. 10.42.92.20

can you post your XMl config. Do you have two adapters one for external and one for internal? your are using DT only? Is the DT connecting fine? what can you ping?

did you reboot the server? route -p ADD 0.0.0.0 MASK 0.0.0.0 (external nic gateway) You will need a full reboot.

Try adding the following persistent routes route -p ADD 10.0.0.0 MASK 255.0.0.0 (10.42.92.2 or whichever is your internal NIC gateway) route -p ADD 192.168 .0.0 MASK 255.0.0.0 (10.42.92.2 or whichever is your internal NIC gateway) route -p ADD 172.16.0.0 MASK 255.0.0.0 (10.42.92.2 or whichever is your internal NIC gateway)

on your AOVPN server do a route print and share the output.

This is when we are using a non lgfl provided 10. * range. I was planning to use a 192.168.20 .* range so they asked to NAt before it comes to the router/firewall.

So we had an issue with the same VLAN IP on all switches. I removed everything from the core and the minute i plugged in the first stack i would get loads of duplicate IP's. if the VLAN IP on the edge switch is the same as the core it will give you a duplicate IP. We then changed the VLAN IP to a new IP in the subnet. VLAN was designed like below vlan 10 - between core and LGFL LGFL - 10.24.1.1 - Core - 10.24.1.2 /30 subnet Management /29 Subnet for eg. core -10.24.1.9 Stack 1 10.24.1.11 Stack 2 10.27.1.13 Previously it was Management /29 Subnet for eg. core -10.24.1.9 Stack 1 10.24.1.9 Stack 2 10.27.1.9 - So we were getting a duplicate IP across all VLANS as we had the same design across all.

@snagrat have you configured Guest wifi on the cambium? We are on LGFL who want us to NAT before we get to the router. Have you done this? We only have a SG550X as a core switch. Anyway the cambium can do this?

Than you Sir we have it up and running now. Much appreciated.

No have not done this. We are using the cloud controller. Where do i set this. Also our AP are receiving IP adress from VLAN 30. Should that be set for the native vlan

Hi All we have recently implemented VLANS and are using cambium wifi. Does anyone have experience setting these up. I have set the AP on a trunk port and and native vlan set after which the Ap was receiving an IP from the pool. If i set the ssid to vlan 60 no clients can receive any IP address. What i have tried also is setting a new vlan on the AP itself and setting the NEtwork to trunk on the AP with default vlan 30 and additional vlans 60. ( in this way the ap is not visible on the controller). has anyone configured this correctly? We are using CNMaestro as the cloud controller.