#Icefloor mac review how to#
#Icefloor mac review mac os x#

Everything worked fine before I 'upgraded' to Mountain Lion Server which I now recognise was a mistake, but I had to replace the server and it won't run anything earlier than 10.8. I'm a really small business, and I'm looking for a really simple solution.

#Icefloor mac review how to#

I just need to figure out how to configure it.

#Icefloor mac review mac os x#

Out of the box, Mac OS X Server 10.8 can't do that any more, so that's the reason for using IceFloor.Д¬learly this is nothing more than a configuration issue - everything works fine with IceFloor turned off - and everything except wireless DHCP works fine with it turned on. One of the things the provider hates is an open MySQL port - they insist that we tie MySQL down so it can only be accessed from specific IP addresses. I need the server firewall because our network has to comply with PCI-DSS (payment card industry regs) which means our network has to be regularly scanned for security. That's why I switched off DHCP on the Netgear. Running two DHCP servers on the same subnet is not such a great idea? Some of our devices have IP reservations on the OS X DHCP server, so I would have no way of making sure that those devices get their IP address from the Mac box rather than the Netgear. I will try opening port 68 to the world instead of just the subnet, to see what happens. Presumably all the wireless devices which are trying to obtain an IP address. Many devices with different MAC addresses appear in the log.

MrHoffman - the log entry I showed was just an example. But I'm guessing that because the firewall is between the Netgear and the DHCP server, I need some other ports open for the devices to get an IP address. The mobile devices will connect directly to the wireless router, so the firewall on the server should not have any effect on their ability to make a connection to the router. With IceFloor switched on, wireless clients are unable to get an IP address. With IceFloor switched off on the server, wireless clients can connect to the Netgear and get an IP address from the DHCP server on the Mac OS X Server. The LAN port of the Netgear is on the same subnet as the server and clients. The Netgear router provides the link to the internet, and we also allow some of our staff to connect mobile devices using its wireless interface. The server runs DNS, DHCP, MySQL, AFP and Kerio Connect (mail server). The network comprises 6 clients (all Mac) and a Mac OS X Server (10.8). Some of this was a bit beyond my knowledge TBA. That'll let you see the packet contents involved, which will then tell you if it's a broken display or a broken packet. Something like Wireshark might provide some insight into what's happening, too. Might specifically add a DMZ, if serving stuff off-network - stuff that can potentially be attacked and breached.ДЄs for your question, if you're really getting (presumably) 0.0.0.0:68 (presumably UDP) requests on your network, then there's something wonky with some component (presumably) requesting a BOOTP operation here - that's not an IP address that should be used with BOOTP, which implies this is either a bad IP address display or is a bad or misconfigured request.Д¬hase down whatever device is using 3c:07:54:5c:dc:20, as a starting point.

When I'm working in this range, typical is a network firewall (PFsense, DD-WRT, or other open source, or a commercial offering such as ZyXEL ZyWALL USG or other such) at the network edge, and the WiFi is configured as one or more Access Points, which in aggregate makes these smaller networks rather simpler to configure and to manage. I've added 0.0.0.0 to the local address list to see if that made a difference, and it didn't. This suggests to me that the DHCP requests from wireless clients are being blocked by the firewall. This address group is associated with Essential system services which includes ports 67 & 68 (all protocols) - I understand that these are the ones needed for DHCP. The server is on 10.0.0.201 and I have a 'local' address group which includes 10.0.0.0/24. However clients which connect to the wireless router do not get an IP address from the server when IceFloor is turned on. The DHCP server on the router is disabled and instead we use the DHCP server bulit into Mac OS X Server 10.8.Д¬lients connected to the LAN via ethernet get an IP address from the DHCP server, no problem. Our server is connected to the internet via a Netgear wireless router.

Unfortunately, with it turned on, I have problems connecting wireless devices to our network. I was very frustrated to lose the Server Admin firewall tool when we upgraded to OS X Server 10.8 in our small office fortunately IceFloor has helped me to rebuild a firewall for blocking specific ports.