Question : RPC Server Not responding, AD resolving to wrong IP address

Experts, Please Help:

Facts:
- Windows SBS 2003 installed 12/19/08. Base install complete
- Client had new internet service installed on 1/19/09. New static IP, new internal IP addresses
- Moved server to new connection (2 wire DSL router
- Added a second NIC (3COM) to take advantage of sttic IP and Windows FW
- System takes much longer to "Prepare Network Connections" than before (up to 20 min)
- Removed second NIC and decided to use port forwarding as a resolution to the problem.
- The following is working as expected
- Outbound Internet (ping, web surfing, nslookup)
- Inbound port forwarding (RDP into server from internet, Ping from Internet)
- Local file and print services
- Single server set up for a home business user
Problem:

- When i tried to run the SBS Connect to the Internet Wizard, all step completed except:
- Email setup, Message says RPC service is not running
- Ran DCDiag and the first check fails.
- Apears that AD is resolving "ServerName" to old IP 192.168.0.14
- ServerName should resolve to 192.168.1.127

Steps I have taken
- Walked through all DNS setting (or so I think) and removed references to old IPs
- Ran Net Diag and reparied errors found
- Checked WINS and DNS resolution (NSLOOKUP), resolved fine with Server DNS
- DNS name resolution does not resolve when I run NSLOOKUP aginst the 2Wire DNS server
- Ran DCDIAG and I see that AD is still resolving to the old address.

Question:
- Where is this record held that AD is the only thing (apparently) resolving to this old address. Doesn't AD use the SBS DNS to resolve names?
- Would this cause the RPC service to fail, or trick the server into thinking RPC is unavailable.
- Note RPC service is running on the server, but errors 1053 are reported. Exchnage reports RPC unavailable when trying to start.

Thats it for now. How can I find out where AD is getting theis address?

Thanks,

Code Snippet:

         
           
           
             Performing initial setup:
   * Verifying that the local machine srvcorp1, is a DC. 
   * Connecting to directory service on server srvcorp1.
   Server srvcorp1 resolved to this IP address 192.168.0.14, 
   but the address couldn't be reached(pinged), so check the network.  
   The error returned was: Error due to lack of resources.  
   This error more often means that the targeted server is 
   shutdown or disconnected from the network
   * Collecting site info.
   * Identifying all servers.
   * Found 1 DC(s). Testing 1 of them.
   Done gathering initial info.
           
         

Open in New Window Select All

Answer : RPC Server Not responding, AD resolving to wrong IP address

Im not sure where it gets it from. I would have just assumed DNS myself. Could it be that there is a host entry in windir/system32/drivers/dhcp/hosts for your server and its using it?