Here's the IPCONFIG /all I get from my notebook as a client on the network (No, I
didn't choose this IP addressing scheme):
Windows IP Configuration
Host Name . . . . . . . . . . . . : DET-KSG-LAP001
Primary Dns Suffix . . . . . . . : scgab.com
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : scgab.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VM Network Connection
Physical Address. . . . . . . . . : 00-08-02-D5-F9-3F
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.0.1.117
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.1.201
DHCP Server . . . . . . . . . . . : 10.0.1.201
DNS Servers . . . . . . . . . . . : 10.0.1.201
Primary WINS Server . . . . . . . : 10.0.1.201
Secondary WINS Server . . . . . . : 10.0.2.200
Lease Obtained. . . . . . . . . . : Thursday, September 16, 2004 12:20:45 PM
Lease Expires . . . . . . . . . . : Friday, September 24, 2004 12:20:45 PMThis one is from the Exchange Server: Windows IP Configuration Host Name . . . . . . . . . . . . : mango Primary Dns Suffix . . . . . . . : honolulu.com Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : honolulu.com Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible) Physical Address. . . . . . . . . : 00-B0-D0-17-56-BC DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 10.0.1.210 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 10.0.1.201 DNS Servers . . . . . . . . . . . : 10.0.1.201 Primary WINS Server . . . . . . . : 10.0.1.201 And this one is from the ISA Server (which is also their internal DNS and has forwarders configured to outside DNS servers): Windows 2000 IP Configuration Host Name . . . . . . . . . . . . : ORANGE Primary DNS Suffix . . . . . . . : honolulu.com Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : honolulu.com Ethernet adapter Internal: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) PRO/1000 XT Network Connection Physical Address. . . . . . . . . : 00-06-5B-F3-D1-B2 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 10.0.1.201 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : DNS Servers . . . . . . . . . . . : 10.0.1.201 Primary WINS Server . . . . . . . : 10.0.1.201 Secondary WINS Server . . . . . . : 10.0.2.200 Ethernet adapter WAN - Internet: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) PRO/100+ Dual Port Server Adapter Physical Address. . . . . . . . . : 00-02-B3-C6-E6-55 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 66.135.233.114 Subnet Mask . . . . . . . . . . . : 255.255.255.248 Default Gateway . . . . . . . . . : 66.135.233.113 DNS Servers . . . . . . . . . . . : 10.0.1.201 PPP adapter RAS Server (Dial In) Interface: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface Physical Address. . . . . . . . . : 00-53-45-00-00-00 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 10.0.1.113 Subnet Mask . . . . . . . . . . . : 255.255.255.255 Default Gateway . . . . . . . . . : DNS Servers . . . . . . . . . . . : 127.0.0.1 Does that help at all? -Ben- ________________________________ From: [EMAIL PROTECTED] on behalf of Deji Akomolafe Sent: Thu 9/16/2004 5:10 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Other people's public domain names in internal Active Directories You are looking at a DNS issue. But, you are focusing on the wrong solution if you focus on the honolulu.com angle. Your server is a DC and ISA server, so it's ostensibly multi-homed. It is very likely registering the external-facing NIC in DNS and your clients (the Exchange) is getting the wrong SRV records for the DC/GC/ISA. There are known issues (and resolutions) with multi-homed DC/DNS servers, moreso when they run RRAS or ISA. Look at some pointers here: http://support.microsoft.com/default.aspx?scid=kb;EN-US;292822 http://support.microsoft.com/default.aspx?scid=kb;KO;275554 http://support.microsoft.com/default.aspx?scid=kb;EN-US;246804 If you post the output of "ipconfig /all" from the ISA server, the Exchange server and at least one other client, we may be able to better help you. Sincerely, D�j� Ak�m�l�f�, MCSE MCSA MCP+I Microsoft MVP - Directory Services www.readymaids.com - we know IT www.akomolafe.com Do you now realize that Today is the Tomorrow you were worried about Yesterday? -anon ________________________________ From: Ben Schorr Sent: Thu 9/16/2004 12:54 AM To: NT System Admin Issues; [EMAIL PROTECTED] Subject: [ActiveDir] Other people's public domain names in internal Active Directories Ran into an interesting situation this week, a client who had a previous consultant set up their small AD and the previous guy assigned it the domain name "honolulu.com" which is, of course, a domain name out in the world. Problem is...it's not their domain name. They have two servers - 1 Exchange server and a GC/DC which also (against my advice) is their ISA server. The GC/DC is Win2000, the Exchange runs Win2K3. Their Exchange server is having difficulty starting up, LDAP errors that hint at DNS problems and I'm wondering if the issue is that internal domain name. The event viewer is full of MSADC errors that say the LDAP server is down. I suspect that maybe it's trying to connect to the LDAP server at the public honolulu.com domain. Their internal DNS seems properly configured and does correctly list their DC/GC server. We can ping the DC/GC from the Exchange server by name or IP address. But Netdiag's DNS tests fail when run on the DC/GC server. If we start the Exchange server it basically hangs at the "Applying Computer Settings" stage. None of the Exchange services start up, due to the LDAP errors, apparently. I've been Googling but I have a feeling I'm looking in the wrong places. Any thoughts? -Ben- Ben M. Schorr Operations Coordinator Stockholm/KSG - Honolulu Phone: (808) 535-1500 Mobile: (808) 351-5084
<<winmail.dat>>
