@mary said in Internet Connection Types - CompTIA A+ 220-1001 Prof Messer: I only get 8 to 10 mbs dl and 1.15mb upload. Country living ugh. One of the very few good things about moving to a "big" city (Cleveland, OH really isn't that big anymore). Internet access went from 10/1 to 100/10, and I've got up to 1gB/60mB available.

@scottalanmiller said in Using IP Addresses - CompTIA A+ 220-1001 Prof Messer: @connorsoliver said in Using IP Addresses - CompTIA A+ 220-1001 Prof Messer: When using an SSL VPN, if the VPN concentrator decrypts the data being sent, wouldn't it be possible for someone to capture the data and also decrypt it? Possible, sure. But very, very hard. The VPN concentrator has the keys, someone intercepting the traffic presumably does not. The point of VPN encryption is to make it so hard to decrypt the data that you don't care if they see it. It's about making something safe enough that we assume we will send it in the open and not worry. So we assume that people capture that data constantly - but we have made it so hard to use, that they can't do it. We more than assume that - we pretty much know the NSA is doing that after the Snowden leaks.

@scottalanmiller said in Assigning IP Addresses - CompTIA A+ 220-1001 Prof Messer: @connorsoliver said in Assigning IP Addresses - CompTIA A+ 220-1001 Prof Messer: How would you know what what IP dresses were available if you weren't using a DHCP server and you were manually entering the IP address and such? They are supplied to you by whomever you bought them from. There is no situation where there isn't someone providing them to you. Unless he was talking about the LAN side. In that case it is the Network Engineer who decides the scope of the LAN and chooses an appropriate sized CIDR and private IP address to use.

But realistically, if you started working in IT full time today, and did normal small business IT work all the time, you might not interact with IPv6 at all for a few years yet.

@coliver said in CentOS can be stupid as well.: I find a good yum clean all tends to fix these types of errors. Yep. I mostly just wanted to point out that even the OS myself and @scottalanmiller are always recommending can do dumb things from time to time as well.

One wrinkle you should be aware of (this needs to be fixed in our web UI!) -- if you change the ZT-managed range from /24 to /23 or /22 you will also need to change it on all the devices. We should add a feature to renumber automatically since right now it's tedious.

@Dashrender said: @JaredBusch said: Correct, you would want to change your servers first. so that devices in the new range can get answers back. In my case, printers are always DHCP reservations. So as soon as I update the DHCP scope that will come down. I've seen you post that before - I think I need to adapt that. Everything is DHCP reservations except the core server infrastructure, HOST, DC, DHCP, and the Router. Exverything else is DHCP reservations, Printers, secondary servers, PBX, everything. Desktops and phones, just normal DHCP.