Ask a questionAsk a question
 

QuestionVista + Messenger +Upnp Problem

  • Saturday, September 15, 2007 3:59 PMWagnard Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    In windows Vista, Messenger is not capable to remove his Upnp mapping on exit like in xp.

    Just want to know why? and if you can fix this bug because my router has more than 10 entry abour MSNMSGR.

    Thanks

     

    Ghislain

All Replies

  • Saturday, October 20, 2007 12:56 PMLyrainn Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    I have the same exact problem with windows xp professional, and I don't really understand why. Also Messenger frequently causes my router upnp service to crash and perhaps I have to restart the router everytime it happens, that's really silly.

    Found no solution on the web either Sad.

  • Thursday, November 15, 2007 12:35 PMharroyo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    im having the very same problem under vista, anyone here can help?
    i think its a messenger problem because every single other program that uses upnp unmaps their ports when i close them.... (except messenger)
  • Monday, December 17, 2007 8:21 PMWagnard Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    Well it seem that Microsft doesnt really care about our problem....

    Verry sad.

     

  • Wednesday, February 06, 2008 6:23 PMShaded Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    im getting the exact same problem with vista... my whole wireless connection just totally drops.. has their been any foward movement on this matter yet?
  • Sunday, October 25, 2009 8:46 AMStrider Nemesis Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    The same thing has always happened to me. Cleaning up every "MSNMSGR" UPnP port mapping from past sessions is very annoying. The interesting part is that Live Messenger does delete the mappings on my Windows XP PC. The Windows Live team seriously needs to fix this.