J
Jukka
Hello.
Our NT4 WINS server is soon going to be shut down for
the very last time. Is there an easy way to export WINS
static mappings and import 'em to Win2k DNS service?
The Win2k box is configured as a primary DNS server
for our client computers. How should I configure
these static mappings to Win2k DNS? None of these
abt. 100 mappings can be found on public DNS servers
and they all point to our customers networks. Some
of these IP addresses are in private networks with
a dialup connection from us and some are public
addresses accessed via Internet but without public
DNS recors.
Someone may suggest installing both WINS and DNS on
same server, but...
....I once had both DNS and WINS on another Win2k server
with two network adapters (routing between two different
networks) and it didn't work at all: workstations didn't
find domain controller (same server) but ping reported
success. Stopping WINS service on that server solved
the problem. It seemed that domain crontroller/netlogon
somehow registered itself on WINS but not in DNS. I don't
know what was the actual cause for this odd behaviour but
I'm afraid something like that may happen again if I start
WINS on this server.
What would be the best solution?
Tnx,
Our NT4 WINS server is soon going to be shut down for
the very last time. Is there an easy way to export WINS
static mappings and import 'em to Win2k DNS service?
The Win2k box is configured as a primary DNS server
for our client computers. How should I configure
these static mappings to Win2k DNS? None of these
abt. 100 mappings can be found on public DNS servers
and they all point to our customers networks. Some
of these IP addresses are in private networks with
a dialup connection from us and some are public
addresses accessed via Internet but without public
DNS recors.
Someone may suggest installing both WINS and DNS on
same server, but...
....I once had both DNS and WINS on another Win2k server
with two network adapters (routing between two different
networks) and it didn't work at all: workstations didn't
find domain controller (same server) but ping reported
success. Stopping WINS service on that server solved
the problem. It seemed that domain crontroller/netlogon
somehow registered itself on WINS but not in DNS. I don't
know what was the actual cause for this odd behaviour but
I'm afraid something like that may happen again if I start
WINS on this server.
What would be the best solution?
Tnx,