Why is MS trying to access my Port 3089?

  • Thread starter Thread starter Karl Andrews
  • Start date Start date
K

Karl Andrews

Starting around 2150 EDT Sunday, ZoneAlarm began blocking incoming
TCP(flags:A) packets from 207.46.106.171:1863 and trying to access my
Port 3390. Then the source shifted to 207.46.106.45:1863 and tried to
get into Port 3042.

According to DNSstuff.com, this is Microsoft. Is this MS checking up to
make sure I'm not cheating on my copy of XP? What will happen if I
continue to block these packets?

- Karl
--
 
We will send in the Black Helicopters and hunt you down like a dog.

MS Police
 
That's MSN messenger (port 1863)... the server may have thought you were
running MSN (and maybe you were!) and was trying to verify this. Perfectly
legitimate. Some people take offense when a remote sites tries a connection
but this is the way the Internet was designed to work. It's only considered
malicious if someone tries to scan multiple ports or attempt to use an
exploit on a certain port.
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

svchost communication concerns - Who is it talking to. 10
what open ports are required by access 2003? 1
Microsoft Word try to access Port 53 about every 2 seconds 1
Log: TCP connection denied from 64.4.19.253:80 to 192.168.0.8:1723 4
RDP to Internal Ip with ICS Port Forwarding 3
winlogon.exe attempting to access photobucket.com 7
Inbound filter for preventing access to certain ports except from local subnet 3
trying to port forward 3

Back
Top