Re: Global Catalog / Domain Controller loses connection to Exchang



Well the secondary NIC's have anways been disabled... I just enabled them for
this test.. Originally i believe they were putin there for redundancy just
incase...

Should i delete the IP routing? Will that have adverse affects? I have
full backups just incase. There should be no set routes for anything on my
network.. It should flow free so to speak.
--
Network Administrator
Simon Paston & Sons Agency


"Miha Pihler [MVP]" wrote:

Hi,

In general Active Directory server should not be multihomed (multiple
NIC) -- (not a recommended configuration). There are quite a few problems
when domain controller is multihomed... Here are few of them...

Troubleshooting browser Event ID 8021 and 8032 on master browsers
http://support.microsoft.com/?id=135404

Clients cannot log on to domain controllers that are Windows Server
2003-based DNS servers, and network interfaces that are not registered in
DNS can still perform dynamic updates
http://support.microsoft.com/default.aspx?scid=kb;en-us;832478

--
Mike
Microsoft MVP - Windows Security

"Chris Baldassano" <ChrisBaldassano@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:8DDD4FFB-509F-4A55-AB32-5462863A07F1@xxxxxxxxxxxxxxxx
An Additional note:

I enabled the secondary NIC's (File2k3 @ 192.168.1.20, MAIL2k3 @
192.168.1.21) and Added the DNS Record in the DNS Lookup Zones...

Mail can now ping File Perfectly to 192.168.1.20, but it still times out
on
192.168.1.3...

This is not acceptable because the /20 address is also going thru a 100
meg
switch and not the gigabit router.. just an FYI.

I did a ipconfig /flushdns on the mail2k3 server so it would see the DNS
change.

This is VERY Strange.
--
Network Administrator
Simon Paston & Sons Agency


"Chris Baldassano" wrote:

I can not ping by IP, Or by Name from mail2k3 to File2k3... But the other
way
around it works perfectally fine (ip or name)...

Now both machines have Dual Gigabit NIC's (Onboard and a 3com) and the
secondary one is just not connected... I am gonna hook them up today to
see
if it is a NIC issue.. (I doubt it, there would be other factors)...

Little more background:

-File2k3 is our DNS server with the proper ISP DNS's forwarded...
-File2k3 is our Global Catalog, and Domain Controller

-Mail2k3 WAS a domain controller, that was taken down by 2 microsoft
tech's
about 5 days ago on a $245 Support Call.. They did all the proper steps
to
make it Just an exchange server and not anything else.



Here is the IP config for each machine..

FILE2K3:

Windows IP Configuration

Host Name . . . . . . . . . . . . : file2k3
Primary Dns Suffix . . . . . . . : pastongroup.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : pastongroup.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : pastongroup.com
Description . . . . . . . . . . . : 3Com Gigabit NIC
Physical Address. . . . . . . . . : 00-0A-5E-1A-01-41
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.3

MAIL2K3:



Windows IP Configuration



Host Name . . . . . . . . . . . . : mail2k3
Primary Dns Suffix . . . . . . . : pastongroup.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : pastongroup.com



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. . . . . . . . . . . . : 192.168.1.114
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com Gigabit NIC
Physical Address. . . . . . . . . : 00-0A-5E-1A-02-C3
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.30
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.3

***

Here is the ping from Mail2k3 to File2k3:

Pinging file2k3.pastongroup.com [192.168.1.3] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.3:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

And here is From FILE2k3 to MAIL2k3:

Pinging mail2k3.pastongroup.com [192.168.1.30] with 32 bytes of data:

Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
Reply from 192.168.1.30: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.30:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

***

Now here is what I notice when I do a NETSTAT -A on mail2k3... there are
a
ton of ports in a CLOSE_WAIT state, which has to be why the pings arent
getting thru and the LDAP etc is failing...

FROM MAIL2K3 (Netstat -a) spit to a txt file.

Active Connections

Proto Local Address Foreign Address State
TCP mail2k3:smtp mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:http mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:epmap mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:https mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:microsoft-ds mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:593 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:691 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:1029 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:1033 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:1037 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:1149 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:1160 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:1166 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:pptp mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:3389 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:6001 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:6002 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:6004 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:7930 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:12174 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:34571 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:34572 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:34573 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:38292 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:48974 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:48975 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:48976 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:48977 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:48981 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:48998 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:1031 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:1179 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:http ten11.bwc.na.blackberry.net:34159
TIME_WAIT
TCP mail2k3:netbios-ssn mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:netbios-ssn ext211.pastongroup.com:1667 ESTABLISHED
TCP mail2k3:microsoft-ds ext286.pastongroup.com:2879 ESTABLISHED
TCP mail2k3:microsoft-ds ext263.pastongroup.com:1702 ESTABLISHED
TCP mail2k3:microsoft-ds ext290.pastongroup.com:1115 ESTABLISHED
TCP mail2k3:microsoft-ds ext292.pastongroup.com:2457 ESTABLISHED
TCP mail2k3:microsoft-ds ext206.pastongroup.com:3725 ESTABLISHED
TCP mail2k3:microsoft-ds ext273.pastongroup.com:4323 ESTABLISHED
TCP mail2k3:691 mail2k3.pastongroup.com:48987
ESTABLISHED
TCP mail2k3:691 mail2k3.pastongroup.com:48997
ESTABLISHED
TCP mail2k3:691 mail2k3.pastongroup.com:49052
ESTABLISHED
TCP mail2k3:691 mail2k3.pastongroup.com:49055
ESTABLISHED
TCP mail2k3:1079 web2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:1080 web2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:kpop file2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:1150 web2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:1288 file2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:pptp ool-457251fd.dyn.optonline.net:1151
ESTABLISHED
TCP mail2k3:pptp ool-457b9bc5.dyn.optonline.net:2912
ESTABLISHED
TCP mail2k3:1788 web2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:2638 web2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:2740 file2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:3389 ext288.pastongroup.com:3032 ESTABLISHED
TCP mail2k3:3908 web2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:3916 file2k3.pastongroup.com:3268 ESTABLISHED
TCP mail2k3:3918 file2k3.pastongroup.com:3268 ESTABLISHED
TCP mail2k3:3919 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3920 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3921 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3922 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3923 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3924 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3925 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3926 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3927 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3929 file2k3.pastongroup.com:3268 ESTABLISHED
TCP mail2k3:3930 file2k3.pastongroup.com:3268 ESTABLISHED
TCP mail2k3:3935 file2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3936 file2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3937 file2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3938 file2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3939 file2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3940 file2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3942 file2k3.pastongroup.com:3268 ESTABLISHED
TCP mail2k3:3946 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3991 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3998 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:4459 file2k3.pastongroup.com:3268 ESTABLISHED
TCP mail2k3:4908 file2k3.pastongroup.com:3268 ESTABLISHED
TCP mail2k3:5217 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5325 file2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5377 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5426 file2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:5515 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5535 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5741 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5769 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5771 file2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5778 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5800 file2k3.pastongroup.com:netbios-ssn
ESTABLISHED
TCP mail2k3:5888 ext240.pastongroup.com:netbios-ssn
TIME_WAIT
TCP mail2k3:5901 file2k3.pastongroup.com:epmap TIME_WAIT
TCP mail2k3:5908 ext286.pastongroup.com:microsoft-ds
ESTABLISHED
TCP mail2k3:5915 192.168.1.200:9100 TIME_WAIT
TCP mail2k3:5917 ext292.pastongroup.com:microsoft-ds
ESTABLISHED
TCP mail2k3:5923 ext263.pastongroup.com:microsoft-ds
ESTABLISHED
TCP mail2k3:5928 file2k3.pastongroup.com:epmap TIME_WAIT
TCP mail2k3:5930 web2k3.pastongroup.com:ldap TIME_WAIT
TCP mail2k3:5931 file2k3.pastongroup.com:ldap TIME_WAIT
TCP mail2k3:5932 file2k3.pastongroup.com:3268 TIME_WAIT
TCP mail2k3:5933 web2k3.pastongroup.com:ldap TIME_WAIT
TCP mail2k3:5934 file2k3.pastongroup.com:domain TIME_WAIT
TCP mail2k3:5935 file2k3.pastongroup.com:domain TIME_WAIT
TCP mail2k3:5937 file2k3.pastongroup.com:microsoft-ds
ESTABLISHED
TCP mail2k3:5940 web2k3.pastongroup.com:ldap TIME_WAIT
TCP mail2k3:5941 web2k3.pastongroup.com:microsoft-ds
ESTABLISHED
TCP mail2k3:47666 file2k3.pastongroup.com:3268 CLOSE_WAIT
TCP mail2k3:48987 mail2k3.pastongroup.com:691 ESTABLISHED
TCP mail2k3:48997 mail2k3.pastongroup.com:691 ESTABLISHED
TCP mail2k3:48998 ext286.pastongroup.com:2130 ESTABLISHED
TCP mail2k3:48998 ext228.pastongroup.com:4869 ESTABLISHED
TCP mail2k3:48998 ext263.pastongroup.com:1148 ESTABLISHED
TCP mail2k3:48998 EXT285:2018 ESTABLISHED
TCP mail2k3:48998 ext270.pastongroup.com:1190 ESTABLISHED
TCP mail2k3:48998 ext256.pastongroup.com:2208 ESTABLISHED
TCP mail2k3:48998 ext290.pastongroup.com:1141 ESTABLISHED
.



Relevant Pages

  • distribution groups dont deliver to some addresses
    ... I've checked that the server has a valid PTR on reverse DNS. ... TCP test succeeded. ... 221 MC8-F13.hotmail.com Service closing transmission channel ...
    (microsoft.public.exchange.admin)
  • Re: distribution groups dont deliver to some addresses
    ... > I've checked that the server has a valid PTR on reverse DNS. ... > TCP test succeeded. ... > Microsoft's computer network is prohibited. ...
    (microsoft.public.exchange.admin)
  • Re: dcdiag errors
    ... Is the second DC also Global catalog server? ... For DC1 set preferred DNS to itself and secondary the other. ... Connection-specific DNS Suffix. ...
    (microsoft.public.win2000.active_directory)
  • Re: DNS Issues?
    ... My ISP's DNS servers were correctly in the forwarders tab. ... Tools - DNS - rclick server name - properties and see if the ISP's dns ... settings are in the forwarders tab. ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.sbs)
  • Re: Global Catalog / Domain Controller loses connection to Exchang
    ... Clients cannot log on to domain controllers that are Windows Server ... DNS can still perform dynamic updates ... Connection-specific DNS Suffix. ... TCP mail2k3:microsoft-ds mail2k3.pastongroup.com:0 LISTENING ...
    (microsoft.public.windows.server.networking)