DDNS registration port.

[Yuriy]

Hello All.
Can anyone tell me what port is used to register in
Windows 2000 DNS by Windows 2000 clients? I thought that
it is using port 53 but now I'm in doubt now as Windows
2000 Professional clients do not register in DNS at all
although they all can resolve DNS names via configured DNS
servers with no problems. Currently all client name
resolution is done through WINS. Here is my configuration:

Domain controllers: Windows 2000 Server SP4
DNS: Active Directory-integrated.
Allow dinamic Updates: Yes

Servers on the same subnet can register with DNS with no
problems.
Windows 2000 clients configured to register with DNS in
TCP/IP properties and located on different subnet.
IPCONFIG/REGISTERDNS don't make any difference. Subnets
devided by Nortel switch.
My guess is something on the switch preventing clients to
register but I do not get a lot of help from my networking
guys. I have to identify source of the problem myself.

 

[Ace Fekay [MVP]]

Answers inline in your post below...

In

Hello All.
Can anyone tell me what port is used to register in
Windows 2000 DNS by Windows 2000 clients? I thought that
it is using port 53

It maybe be using an initial emphereal port (above UDP 1023) that connects
to UDP 53. This is common MS communication among Windows machines. Kind of a
pain if you ask me when it comes to firewalls.

but now I'm in doubt now as Windows
2000 Professional clients do not register in DNS at all
although they all can resolve DNS names via configured DNS
servers with no problems. Currently all client name
resolution is done through WINS.

WINS does NOT register clients. However, when configured properly, DHCP
will. In the default settings, a client that can register will register
itself, unless you change the settings to have DHCP register on behalf of
all clients.

Here is my configuration:

Domain controllers: Windows 2000 Server SP4
DNS: Active Directory-integrated.
Allow dinamic Updates: Yes

Servers on the same subnet can register with DNS with no
problems.
Windows 2000 clients configured to register with DNS in
TCP/IP properties and located on different subnet.
IPCONFIG/REGISTERDNS don't make any difference. Subnets
devided by Nortel switch.
My guess is something on the switch preventing clients to
register but I do not get a lot of help from my networking
guys. I have to identify source of the problem myself.

Maybe it's the empereal ports. If the rouyter (sounds like a layer 3 Nortel
switch) is blocking certain types of traffic, it may be the issue. Need to
allow UDP53 and TCP53 and UDP > 1023. I know, don't argue. I didn't make the
rules. I just follow them.

May also be it's the client's Primary DNS Suffix (found in My
COmputer/Properties/Name tab/More). A machine will register into a zone name
based on that name. If different, and the zone doesn't exist, well, you know
what I mean...

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Alan Wood [MSFT]]

Please NOTE.. UDP connections use 1 PORT. Meaning the UDP connection for
the Dynamic Update is over Client UDP 53 and Server UDP 53.

Thank you,

Alan Wood[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Ace Fekay [MVP]]

In

Please NOTE.. UDP connections use 1 PORT. Meaning the UDP connection
for the Dynamic Update is over Client UDP 53 and Server UDP 53.

Thank you,

Alan Wood[MSFT]

This posting is provided "AS IS" with no warranties, and confers no
rights.

Curious Alan, why the emphereal port?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory