DHCP Server uncontactable on SBS server
Hello
I was browsing through event veiwer and came accross this error under the system tab,
Unable to contact a DHCP server. The Automatic Private IP Address 169.254.57.132 will be assigned to dial-in clients. Clients may be unable to access resources on the network.
I have also noticed that once an IP address is changed on one of the computers (for example network cable unpluged and pluged into a router to configure it) when the network cable is pluged back into the computer (for the main network) the DHCP server on SBS is not contactable and the NIC assigns itself the ip address above 169.254.57.132
Has anyone come accross this issue before?
Regards
Gavin McMillan
I was browsing through event veiwer and came accross this error under the system tab,
Unable to contact a DHCP server. The Automatic Private IP Address 169.254.57.132 will be assigned to dial-in clients. Clients may be unable to access resources on the network.
I have also noticed that once an IP address is changed on one of the computers (for example network cable unpluged and pluged into a router to configure it) when the network cable is pluged back into the computer (for the main network) the DHCP server on SBS is not contactable and the NIC assigns itself the ip address above 169.254.57.132
Has anyone come accross this issue before?
Regards
Gavin McMillan
Saineolai
If ISA on the SBS server is not configured correctly it can prevent client PCs contacting the DHCP service.
ASKER
I do have ISA Installed, I am still working on configuring it, i am also having problems with FTP now too, which is being a hassel.
Do you know of a good guide that can help me configure ISA to work easily with all the features needed?
I had it configured and working well, but since upgrading to ISA 2004 have had problems.
Regards
Gavin
Do you know of a good guide that can help me configure ISA to work easily with all the features needed?
I had it configured and working well, but since upgrading to ISA 2004 have had problems.
Regards
Gavin
ASKER
Well, it turns out that this is at least partially my fault. You see, when I set up ISA 2000, I never let ISA build the LAT table for me - I always manually specified the internal address range I wanted. So for an SBS using the default IP of 192.168.1.2, I would specify a LAT of 192.168.1.1 to 192.168.1.254.
ISA 2004 varies from ISA 2000 in that it firewalls all network interfaces, including the internal interface. My DHCP problem was that DHCP requests happen via the broadcast address of .255 - since my LAT entry ended at .254 - ISA blocked the traffic, so the DHCP Server never received the client request, and the client thus was unable to pull an IP via DHCP.
The resolution for this problem is to:
Go into your ISA management console, expand the configuration node and then select the Networks node, then edit the internal listing to state for example 192.168.1.1 to 192.168.1.255 otherwise ISA will block any broadcasts as they are performed on 192.168.1.255 (which until changing it wasnt part of your internal network).
ISA 2004 varies from ISA 2000 in that it firewalls all network interfaces, including the internal interface. My DHCP problem was that DHCP requests happen via the broadcast address of .255 - since my LAT entry ended at .254 - ISA blocked the traffic, so the DHCP Server never received the client request, and the client thus was unable to pull an IP via DHCP.
The resolution for this problem is to:
Go into your ISA management console, expand the configuration node and then select the Networks node, then edit the internal listing to state for example 192.168.1.1 to 192.168.1.255 otherwise ISA will block any broadcasts as they are performed on 192.168.1.255 (which until changing it wasnt part of your internal network).
Running the Configure Email and Internet Connection Wizard will accomplish much of this configuration. And that's where you should start on an SBS, since it will integrate the configuration with other SBS services.
Jeff
TechSoEasy
Jeff
TechSoEasy
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.