Kudos0

ms-wbt-server(3389).

I looked at my logs and

 

I received an unsolicited inbound connection via port 3389 from  64.217.219.120 which is an address in the range from my ISP, I had set a rule to block all unsolicited  inbound on this port from all outside sources, how can this be happening then? 

 

 

 

Connection: 64.217.219.120: 62852.
to MY-PC: ms-wbt-server(3389).
0 bytes sent.
0 bytes received.
0.007 elapsed time

Replies

Kudos0

Re: ms-wbt-server(3389).

I looked at my logs and

 

I received an unsolicited inbound connection via port 3389 from  64.217.219.120 which is an address in the range from my ISP, I had set a rule to block all unsolicited  inbound on this port from all outside sources, how can this be happening then? 

 

 

 

Connection: 64.217.219.120: 62852.
to MY-PC: ms-wbt-server(3389).
0 bytes sent.
0 bytes received.
0.007 elapsed time

Kudos0

Re: ms-wbt-server(3389).

I thought setting the firewall rule to block all inbound would stop this?
Kudos0

Re: ms-wbt-server(3389).

NY1986:

There are a great many systems and services that you can't block.  The key word is unsolicited.  You may think that you are not soliciting these connections but your computer is and it requires them.  The trick  is to know which services should have access to what ports and when.  In order to do that you will have to read this:

http://support.microsoft.com/default.aspx?scid=kb;en-us;832017#5

I'm quite certain that most of us are not going to want to go through a port by port explanation.  There are far too many.

Under certain circumstances profanity provides relief denied even to prayer.Mark Twain

This thread is closed from further comment. Please visit the forum to start a new thread.