Upgrading Nt4 to Win2K through NAT .... not possible?
This is a discussion about Upgrading Nt4 to Win2K through NAT .... not possible? in the Windows Networking category; Trying to keep this short, We have a main office with a PDC and BDC, along with 6 locations that have a BDC. We use cisco routers with NAT enabled. All are running NT4. We upgraded the servers at the main office to Win2k.
Trying to keep this short, We have a main office with a PDC and BDC, along with 6 locations that have a BDC. We use cisco routers with NAT enabled. All are running NT4. We upgraded the servers at the main office to Win2k. DDNS was a learning experience, but we got there.
When we tried to upgrade the remote BDC to Win2K, we couldn't establish the trust needed with the Win2K servers at the main office. We played with DNS and still couldn't get it. We ended up calling MS and they said that the problem is that Win2K can't/won't validate or establish trusts through NAT. In other words, as long as NAT was in place internally, there was no way we could run a Win2K network.
Has anyone else run into this problem, or better yet, is there a workaround? I would hate to re-design the entire network in order to upgrade to Win2K.
Thank you!
When we tried to upgrade the remote BDC to Win2K, we couldn't establish the trust needed with the Win2K servers at the main office. We played with DNS and still couldn't get it. We ended up calling MS and they said that the problem is that Win2K can't/won't validate or establish trusts through NAT. In other words, as long as NAT was in place internally, there was no way we could run a Win2K network.
Has anyone else run into this problem, or better yet, is there a workaround? I would hate to re-design the entire network in order to upgrade to Win2K.
Thank you!
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
