Join Us!

Spaces are allowed; punctuation is not allowed except for periods, hyphens, and underscores.
A valid e-mail address. All e-mails from the system will be sent to this address. The e-mail address is not made public and will only be used if you wish to receive a new password or wish to receive certain news or notifications by e-mail.
CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
Image CAPTCHA
Enter the characters shown in the image.

Login

Enter your Project Envision username.
Enter the password that accompanies your username.
Request new password

SBS 2008 BPA DNS A resource record points to incorrect IP address

When running Small Business Server 2008 Best Practices Analyzes, you can see that mysterious error.
DNS A resource record points to incorrect IP address

The host (A) resource record points to the incorrect IP address 192.168.1.59192.168.1.2. The record should point to 192.168.0.2.

In the BPA reports it is denoted as Critical. The first strange thing is that two IP addresses become one: “address 192.168.1.59192.168.1.2”, it is not a typo. What is the source of this error?
The most common cause of that critical alert is that we enable Routing and Remote Access on our SBS server. To verify that Open Routing and Remote access and verify that the first IP address, in this example “192.168.1.59” is assigned to Internal Interface in Routing and Remote Access.

After above verification you have to options, the first one is to ignore that alert, the second is to run Small Business Server Best Practices Analyzer Scans when Routing and Remote Access is stopped. To stop Routing and Remote Access issue following command “net stop remoteaccess” to start it after the scan is done “net start remoteaccess”. If you prefer PowerShell instead of net stop and net start you can use Stop-Service and Start-Service cmdlets.

If you need help with your SBS Contact Us

Categories:

SBS 2008 BPA DNS A resource record points to incorrect IP addres

The reason for the error is that you are probably scanning over a vpn connection. It's been bugged with Microsoft so hopefully they will fix it in the next def updates.