Question Locked

Domain Controller TCP SYN ACK activity

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

My firewall is logging TCP SYN ACK activity from the domain controller that is constant. I have pasted a sample of the log below. It doesn't do every port but seems to start at 1096 go through some not all of the ports to 4976 then restarts with 1096. There are a couple of instances of activity attempts to 29054.

IP: discard from 10.67.10.30 port 139 to 169.254.4.124 port 1925 TCP SYN ACK (Attempt to send TCP packet on an unopen port)
IP: discard from 10.67.10.30 port 139 to 169.254.4.124 port 1817 TCP SYN ACK (Attempt to send TCP packet on an unopen port)
IP: discard from 10.67.10.30 port 139 to 169.254.4.124 port 1925 TCP SYN ACK (Attempt to send TCP packet on an unopen port)

The Domain Controller is part of AD and runs, DHCP, DNS and WINS. Before anyone guesses it is WINS causing the activity, WINS has been running for a long time without causing this.

Anyone have any idea what is going on and how I can stop this DC behavior?

Thanks,

Jeanette Hartwick
IS Manager

2 replies

by bens

That 169.254.4.124 is an automatic private IP address - which normally is assigned by Windows if a DHCP server is unavailable. I would locate that 169.254.4.124 first to see where that might be coming from. You could try running nbtstat -A 169.254.4.124 from command line to find a name for the machine in question.

Just an assumption, but I'm thinking 169.254 is trying to renew an IP from your DHCP server (if that is the 10.67 address) by sending a SYN. Your DHCP server sends SYN/ACK to ack the request.

This discussion is closed to new replies.