We ran the SBS 2011 install via Answer File for this new network setup that we are working on.
They already had a peer to peer setup in place with SonicWall devices serving DHCP and acting as edge.
Two Fonality servers were set up in redundant mode.
So, prior to running the SBS OS install we deleted the SonicWall DHCP subnet scope to make sure we had SBS based DHCP this morning.
Well, no go.
We had the SBS is Installed Successfully green check mark but no system had an IP address.
Checking in the SBS Native Tools console we saw that DHCP had no scope.
We ran the Internet Address Wizard and:
The SBS wizard found a DHCP server at the Fonality’s primary server IP. We logged into the admin site with no DHCP Server options anywhere to be found.
In the end we needed to call them to have them log in via their own backend management and turn the DHCP services off for both the primary and secondary servers.
Moral of the story: If there are any third party devices and/or services in place before, or coming in afterwards, verify with the vendors whether anything in them will conflict with a Windows Domain/DNS/DHCP setup and have their “This is how you set things up on a Windows Domain/DNS/DHCP based network” documentation at hand.
The Fonality and other systems on this particular network require DHCP scope options along with custom DNS Forwarders for the phone “domain” among other things.
Got coffee? ;)
UPDATE: Fonality’s Support Site for DHCP and DNS setup on a Windows Network
Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book
*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.
2 comments:
Is it feasible to have a separate VLAN for the VOIP system? That is often the recommendation for VOIP systems.
Doug,
Not this one. It is actually quite the slick system though the phones only have 100Mbit pass through at this time so a dedicated port for them is in order.
Philip
Post a Comment