Is this an internet connection to an ISP? If so, you are taking a big risk
allowing traffic from the internet through to a domain controller (or any nt
server for that matter). If that is the case, I would rethink the design.
Build a private network with frame-relay or point to point using rfc19
Jim,
My experience with NAT between DCs is you can not use PAT, you have to map
the address of the DCs statically.
If this is internet connection related, why not nat at the internet router?
if this is private address overlapping, you have to give the BDC an address
sperated from other traffic,
I've had tried that method before, however it doesn't work, beside Netbios
port (139), NT must be using different port to communicate between PDC &
BDC. Couldn't figured out which other port NT using.
Here is my layout (didn't work hehe):
PDC (Public IP)
|
|
Internet Cloud
|
I see what you want to do.
I guess you could create a tunnel with soure and destination as the public
address, put your private address on the tunnel, eable routing throught the
tunnel or just use static route. it should work.
But your setup is not secure at all, I believe you already realized.
You need some sort of name resolution. Easiest way would be to setup lmhost
files on both pdc and bdc. Use the #dom keyword. This will also take care
of browsing, which I assume is not working across the router either
mike
Jim Bond <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:
5 matches
Mail list logo
