• 0

MSN Messenger 7.5 (Build 0299) Connection Problem


Question

Recommended Posts

  • 0
HKEY_CURRENT_USER\Software\Microsoft\MSNMessenger

and

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSNMessenger

586421490[/snapback]

Didn't work.

Umm just because it works for most people doesnt mean its not a bug, bug != affect everyone.

I suspect some kind of http filtering or possibly a proxy server is stopping it working.

586421919[/snapback]

No and no. Every other version and every other program works perfectly.

have you tried troobleshooting?

586422029[/snapback]

Yep.

  • 0

try uninstalling it, deleting the directory, running a couple of registry cleaners, search the registry for msn entries, reinstall, try to connect.

if that doesn't work, try

a differnt user account

installing beta .244 and installing final on top

installing 7.0, installing on top

etc, until something works.

  • 0
Run your crap cleaner (scan for issues) fix the issues. Then reboot system then you will be fine

586422211[/snapback]

Already done between installs, after uninstalls, after installing etc.

  • 0
I just find it strange that they didnt have us beta testers test the latest vertion... that doesnt make sence, releasing a build that wasnt tested by beta testers.

586422028[/snapback]

its being beta tested now..by all the wanna be's who think newer is better....lol....there is a new update coming and its not 7.5.0299 :whistle:

  • 0
try uninstalling it, deleting the directory, running a couple of registry cleaners, search the registry for msn entries, reinstall, try to connect.

if that doesn't work, try

a differnt user account

installing beta .244 and installing final on top

installing 7.0, installing on top

etc, until something works.

586422215[/snapback]

I've tried all that :(

  • 0
that's really bizarre. have you tried downloading the installer again? i really don't know what it could be...

586422569[/snapback]

The installer is perfect. Something I noticed from the MSN Messenger Wikipedia article...

MSN Messenger uses the Mobile Status Notification Protocol (MSNP) over TCP (and optionally over HTTP to deal with proxies) to connect to the .NET Messenger Service - a service offered on port 1863 of messenger.hotmail.com. Its current version is 12 (MSNP12), used by MSN Messenger version 7.5 and many other third-party clients. The protocol is not completely secret: Microsoft disclosed version 2 (MSNP2) to developers in 1999 in an Internet Draft, but never released versions 8, 9, 10, 11 or 12 to the public. .NET Messenger Service servers currently only accept protocol versions from 8 and on, so the syntax of new commands from versions 8, 9, 10, 11 and 12 is only known by using sniffers like Ethereal.
  • 0
I'm getting the same problem. I've tried everything mentioned in this thread.

586422841[/snapback]

i have the same problem here as well

tried everything mentioned in this thread :wacko:

586422971[/snapback]

Actually feels good knowing I am not alone with this.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • These features described above are good, but far from what developers like me was eager to get. And that main feature that developers will love it`s the ability to connect to LOCAL AI models running on Ollama. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
    • Wow, Microsoft IS cooking lately... This only shows that they COULD improve, they just chose not to for whatever reasons. That obsession with AI was destroying them from the inside out.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      80
  • Tell a friend

    Love Neowin? Tell a friend!