The laptops in the Young Adult area were taking too long to log into the Cassie system, rendering them usable.
I noticed TeenZone04 and 05 (but not 1-4, which should have tipped me off) still had their static IPs in Sonicwall. The IP is associated with a MAC address. I had previously swapped the wireless access points to VLAN40 to get rid of VLAN50 and removed the wired connections on the laptops since I can have the wireless adapters connect to VLAN40. When I did this, those Sonicwall static IPs had the wrong MAC address. So I deleted those entries and took out the static IPs on the laptop adapters as well. This didn’t work.
I then deleted the Static IPs in the DNS Manager on our DNS Server. Still no luck.
Then I noticed the Print Release Station (PRS) wasn’t on. For whatever reason, when logging into Cassie if that’s off, then the logon takes forever. So I turned it on. Still no luck.
I noticed that the ethernet adapter of the PRS had an “!” next to it. So I checked it out and saw that it was saying there was a duplicate IP on the network. And therein lied the problem. The static IP assigned to the PRS happened to be in the dynamic IP range specified by Sonicwall. So that when the PRS wasn’t on, it handed out that IP to a patron’s laptop.
I changed the PRS DNS entry to use a static IP outside the dynamic range. But because there’s another issue on the network, the Cassie printers defined on the Young Adult laptops were using the IP address, not the server name of the PRS. I had to change each of the printers on each of the laptops to use the new IP. Once that was done, everything was coming up Milhouse.
Networking has never been my forte. I know enough to keep the lights on, as it were, but when things go wrong, it takes me longer than it should to resolve. I followed my predecessor’s precedence and used static IPs for most of the computers. I’m not really sure why.
One “why” I learned through this dealio was why VLAN50 existed. Since we’re using Ubiquity Wireless Access points, we have a Unifi Network Controller. That controller doles out IPs for wireless devices. It was confusion between this, Sonicwall, and the DNS Server that allowed for one of the patron’s devices to nab the PRS IP. This wouldn’t have happened if the wired and wireless networks were on different VLANs. Hence VLAN50 was used for a constantly changing array of devices. But that was an auxiliary mistake. Ultimately, it was the fact that the PRS’s static IP was in the dynamic IP range I specified on Sonicwall. But I was just copying over the Static IPs I found in the DNS Manager when I installed Sonicwall. So I carried over an already conflicting setup.
Ok. So, in case you’re in a similar situation, here are the three pieces of software that I have handling IP addresses on the network. I need to simplify this, big time. When I do, perhaps that will resolve why I can’t reference the Young Adult PRS computer by name and am forced to do so by IP.
- Windows Server DNS Manager
- Sonicwall Network DHCP Server
- Unifi Network Manager
Now I hope the picture at the start of the post makes a wee bit more since.