Windows Forum

Ask something
Discussion Locked

Windows 2000 and tcp connections

0 helpful
5 replies

by rceaser

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a windows nt 4.0 network with workstations at remote locations. I started to upgrade the workstations to windows 2000 pro. The workstations are working fine except the workstations at the remote locations. The users are not experiencing any problems but our router keeps triggering alarms from the windows 2000 workstations. Do anyone know what is happening? This is the information from the router alarm:

Source host = Workstation Name, Workstation IP (1195)
Destination host = Server Name, Server IP (tcp, 455).

The port from the host computers keep changing but port for the destination host stays the same.

Do I need to have something changed on the router because of the windows 2000 workstation because the NT 4 Workstations do not trigger an alarm?

Thanks.

5 replies

by howley

I don't know if you have looked into this but windows 2000 pro by default will try to register itself with a dynamic DNS server. I have seen this cause a lot of traffic before but did not see any issues with routers, but this was not for field offices and the internal routers were not monitored as closely as the ones to the outside. To turn this off:
Go to the properties for the network connection
Go to the TCP/IP properties and choose advanced
choose the DNS tab
At the bottom there is a check box for "register this connections address with DNS"

This setting only generates useless traffic if you are not using a windows 2000 server with dynamic DNS.

Hope this helps!

by rvkempen

This is strange, I'm not sure it has anything to do with ddns, port 455 is owned by creative partners, while port 1195 is still unassigned (www.iana.org).
Please keep me advised if it has to do with ddns

This discussion is closed to new replies.