Firewall Wizards mailing list archives
Re: TCP port 7 traffic from DoubleClick
From: "Timothy K. Ewing" <EwingTK () celera com>
Date: Tue, 13 Jul 1999 16:02:05 -0400
We saw this same kind of behaviour back on May 3, 1999. I contacted Dave Smith at Doubleclick and inquired as to why this was happening. At that time he indicated that his company was using a product called Resonate Global Dispatch, an internet advertising tool, which identifies the closest DNS servers to the client. The program gathers some type of metrics by connecting to DNS servers. He indicated that they had recieved lots of other complaints in addition to mine and that they would probably move to using 'pings' instead. Looks like they may have switched to connecting to the echo port for those systems that have it open (a bad port to have open anyway). I have not called them lately to verify this progression by I suspect that this is what is happening. Timothy K. Ewing Security Analyst Celera Genomics Corp.
Current thread:
- Re: TCP port 7 traffic from DoubleClick, (continued)
- Re: TCP port 7 traffic from DoubleClick James Burns (Jul 07)
- Re: TCP port 7 traffic from DoubleClick C. Harald Koch (Jul 06)
- Re: TCP port 7 traffic from DoubleClick Joseph S D Yao (Jul 12)
- Re: TCP port 7 traffic from DoubleClick Vern Paxson (Jul 06)
- Re: TCP port 7 traffic from DoubleClick Neil Ratzlaff (Jul 09)
- Re: TCP port 7 traffic from DoubleClick Albert Hopkins (Jul 12)
- Re: TCP port 7 traffic from DoubleClick Neil Ratzlaff (Jul 09)
- Re: TCP port 7 traffic from DoubleClick Vern Paxson (Jul 07)
- RE: TCP port 7 traffic from DoubleClick Mason Begley (Jul 08)
- Re: TCP port 7 traffic from DoubleClick ark (Jul 12)
- Re: TCP port 7 traffic from DoubleClick R. DuFresne (Jul 12)
- Re: TCP port 7 traffic from DoubleClick Timothy K. Ewing (Jul 13)
- Re: TCP port 7 traffic from DoubleClick David Lang (Jul 14)