BDC keeps calling out through ISDN router

[Bram Ruizendaal]

Hello,

 

In a small NT domain, PDC and BDC, which are connected through a WAN link (ISDN router Zyxel), the BDC keeps calling out through the ISDN router to the PDC.

I've searched through every Technet article and have applied all that Microsoft recommends in it. (Optimizing WAN networks etc.)

There are no shares or something like that on the BDC that point to the PDC.

But the BDC keeps calling out.

The source ports vary from 1800 throug 1900 but the destination ports are always 139. (Netbios)

What is the cause of these calls and why do they take place?

 

best regards,

 

Bram Ruizendaal

T-ICT B.V.

[Alex Roberts]

Hi Bram,

    This looks like standard functioning for a pdc bdc relationship.  Periodically they are going to replicate their accounts database (sam), as well as any files in the replication folders (logon scripts, etc.).  Because of the nature of ISDN, these calls for replication will probably initiate an isdn call, and your phone bill will be quite high.

    To stop the ISDN call setups, I suppose you could set up filters on your router to define interesting (and thus, call opening) traffic.  You could exclude the traffic the bdc is sending and receiving.  However, this would most likely have a negative impact on those clients trying to authenticate on the bdc side.  You're accounts will not be up to date and such.  If WAN traffic is an issue, you may even want to consider seperate domains and PDC's for the 2 sites, and create trust relationships between the domains so that you can administer them both easily when the link is up.  However, you would then lose fault tolerance for your sam.  I would definatley not have one dc for a domain.

    Also regarding NT4 questions, you may get more responses in the NT 4 RAS newsgroup

 

microsoft.public.windowsnt.protocol.ras

 

Best Regards,

Alex

MCSE, CCNA, CCDA

"Bram Ruizendaal" <bruiz...@t-ict.nl> wrote in message news:O02TZoopAHA.1904@tkmsftngp03...