Page 2 of 2 FirstFirst 12
Results 16 to 22 of 22

Thread: Windows 7:Process System listen to port local:any TCPv6:10243

  1. #16
    Join Date
    Jun 2003
    Location
    NJ
    Posts
    375

    Re: Windows 7:Process System listen to port local:any TCPv6:10243

    I'm having trouble creating your problem, probably because my router is not IPv6 ready at this time, but I have a problem with port 2869. Selecting "Web Server" is not answering the question. Check out your Outpost settings>network rules>system-wide rules. Under "applied after application rules", do you see a rule for port 10243. If not, select custom rule the next time you see the pop-up. I personally don't add rules without a remote address. Local:any=0.0.0.0

  2. #17
    Join Date
    Jun 2003
    Location
    NJ
    Posts
    375

    Re: Windows 7:Process System listen to port local:any TCPv6:10243

    You might also want to block the port until we know what it's used for.

  3. #18
    Join Date
    Mar 2002
    Posts
    11,308

    Re: Windows 7:Process System listen to port local:any TCPv6:10243

    For instructions on how to close a port (system-wide or per specific app), please see this Agnitum KB article: How do I close an open port?.

  4. #19
    Join Date
    Jan 2009
    Posts
    14

    Re: Windows 7:Process System listen to port local:any TCPv6:10243

    ok, and as of minoka's prbl, I installed my win 7 clean slate and Outpost pro as my single software to check this kind of ports ( I had some more and possibly the one you are inquiring as well). I had outpost asking me to allow trafic to certain ports. I found that some of this are required for driver updates but they are as well used by malwares. Since it was a clean install, I allowed all the requests. The courious thing was that installing twice I had the second time I had a new pop up, something about TCpv 6. I hope , the new version of Outpost will solve this problems.

  5. #20
    Join Date
    Feb 2006
    Posts
    46

    Re: Windows 7:Process System listen to port local:any TCPv6:10243

    Anything new here?
    I just dont know what to do now...

  6. #21
    Join Date
    Sep 2008
    Posts
    4

    Re: Windows 7:Process System listen to port local:any TCPv6:10243

    Does anyone have a solution to this yet? Or should I submit a ticket? It changes the address each time.

  7. #22
    Join Date
    Apr 2003
    Posts
    29

    Re: Windows 7:Process System listen to port local:any TCPv6:10243

    Port 10243 TCP is used by WMC to actually stream the media to the PC. Basically, there is a web server on this port. The Digital Media Receiver (DMR) uses UPnP on port 2869 to get a list of the music, video, or photos that are available. When it is ready to play music (for example) it gets the URL of the song from UPnP and then requests it. The port in that URL is port 10243. The web server then streams the music to the DMR on that port.
    Do, Or Do Not. There is No Try...

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. System Attempts to listen to port 80
    By bassbag in forum Outpost Pro FIREWALL General Discussions, Support, and Troubleshooting
    Replies: 10
    Last Post: 07-11-2011, 03:44
  2. outpost.exe as system service (not local)
    By Deshroom in forum Outpost Pro FIREWALL General Discussions, Support, and Troubleshooting
    Replies: 1
    Last Post: 07-13-2006, 04:10
  3. Control System Process
    By fosi in forum Outpost Pro FIREWALL General Discussions, Support, and Troubleshooting
    Replies: 28
    Last Post: 11-02-2003, 22:25
  4. Connects to System process
    By mike.smith in forum Outpost Pro FIREWALL General Discussions, Support, and Troubleshooting
    Replies: 35
    Last Post: 11-12-2002, 17:20

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •