Problem:\n1. Vista workstations are configured for DHCP but cannot get an IP address\nfrom the SBS Server/DC\n2. Vista & XP Workstations cannot access their email via Outlook\n3. Workstations cannot remote desktop to SBS server/Domain controller\n4. SBS/DC Server (ABCSBS01)\n\nWe think the problem is with the DNS setup, however nothing has changed on\nit. Recently We noticed a few\n\nEnvironment:\nâ€¢ Vista SP1 workstations with Office/Outlook 2007\nâ€¢ XP SP2 & SP3 workstations with Office/Outlook 2003\nâ€¢ Win 2003 SBS Server SP2 with Exchange, is Domain Controller & DNS Server\nDHCP Server (SBS/DC) (192.168.0.2 & 192.168.0.8). No Windows firewall\n(ABCSBS01)\nâ€¢ Win 2003 File Server, also a Domain Controller (192.168.0.3). No Windows\nFirewall. (ABCFS01)\nâ€¢ Motorola Surfboard Cable Modem â€“ DHCP is disabled (192.168.100.1)\nâ€¢ Smoothwall firewall (192.168.0.1)\n\nRecent maintenance tasks on server\nThe only maintenance task done on the SBS/DC was to swap the EXCHSRVR disk\nthat contains the MDBData files. No programme file locates were changed.\nAfter stopping the Exchange services, these files were relocated to a new\ndisk and the disk was allocated the same drive letter as the former disk.\nAll the Exchange services start without error and we can access the Exchange\nmail box via OWA on the SBS/DC.\n\nConnectivity tests\n\nWorkstations\nâ€¢ Vista workstations attempt to log on to the SBS and get a 169.254.* IP\naddress.\nâ€¢ On Vista workstations, Connection-specific DNS suffix is blank in\nIPconfig.\nâ€¢ When doing Network Diagnostics, we get Windows cannot find â€œABCSBS01â€\nClick for more information about DNS.\nâ€¢ When doing ipconfig /displayDNS, Name does not exist appears in relation\nto all the DNS servers that are described in our DNS setup (viz ABCSBS01,\nABCFS01, _kerberos._tcp.dc._msdcs.ABC.local,\n_ldap._tcp.dc._msdcs.ABC.local. Many external web sites are listed here also.\nâ€¢ Have done Ipconfig /flushDNS, Ipconfig /degisterDNS\nâ€¢ XP workstations can get a valid 192.168 ip address but cannot access\nExchange via Outlook. Connection-specific DNS suffix is not blank in IPconfig\nâ€¢ If we configure a Vista Workstations with Fixed IP address, it can access\nthe domain resources (files & folders on the file server) but cannot access\nemail on the exchange server. Either a local PST is opened or a workstation\nissues the error Microsoft Exchange server is unavailable. Retry/Work\noffline/Cancel.\nâ€¢ Can remote desktop to the ABCFS01 File server but not to the SBS/DC ABCSBS01\nâ€¢ From any workstation, when we attempt to ping the SBS/DC â€“ via IP address\nor workstation name, we get time-outs\nâ€¢ When doing NSLookup <DC name> we get a DNS request timeout with Server\nUnKnown however the correct Ip address of the DNS server is returned.\nâ€¢ Only some workstations are displayed in Network leaf of Explorer.\n\n\nSBS/DC (ABCSBS01) â€“ Connectivity\nâ€¢ When doing IPConfig, we get 2 IP addresses returned for the same NIC\n(192.168.0.2 & 192.168.0.8). This has been the case for a very long time\nwithout problem. The old IP address that probably was used by an old NIC is\ndisplaying along with the current IP address.\nâ€¢ When pinging itself via w/station name â€“ viz ABCsbs01, we get the valid ip\naddress returned. When we ping that same IP address, we get the workstation\nname returned\nâ€¢ When we ping the additional IP address, we also get successful\nâ€¢ Can access the File server file via Remote Desktop and can access files &\nfolders on the file server\nâ€¢ Can access the internet\n\nDHCP â€“ services are started\nNet Logon services are started pm\n\nI don't believe we have any group policies that would be preventing us from\nlogging in.\n\nDNS Setup\nThe server name ABCSBS01.local appears with every occurrence of the valid\nIIP address (192.168.0.2). The old IP address (192.168.0.8) is also listed\nwith the server name in the DNS setup along with the current IP addressof the\nserver in DomainDNSZones & ForestDNSZones in the DNS setup\n\nWe have done, Ipconfig /FlushDNS, Ipconfig /RegisterDNS, DCDiag /FIX, Net\nstop netlogin, Net Start netLogin.\n\nWhen we run DCDiag again, we still get the error GUID <Long\nNumber>._msdcs.jsr.local) couldn't be resolved, the server name\n(jsrsbs01.jsr.local) resolved to the IP address (192.168.0.2) and was\npingable. Check that the IP address is registered correctly with the DNS\nserver. ABCSBS01 failed test Connectivity\n\nOther DCDiag tests pass.\n\nWhere do we enter the name of the server to overcome the UnKnown error in\nthe DNS name?\n\nWe have looked through the event logs and havenâ€™t found anything that looks\nparticularly informative.\n\nWhere else do we need to check/look to overcome the login problem which I\nbelieve is preventing Access to the Exchange mail boxes via Outlook?