Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Bug in MSN Messenger, confirmation please.

Bug in MSN Messenger, confirmation please.

Scheduled Pinned Locked Moved The Lounge
sysadminhelptutorialtoolsjson
4 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    Gabriel 2
    wrote on last edited by
    #1

    Use proxy server Type: HTTP Proxy Server: Proxy Address Port: 8080 4 - Try to connect to the server. With a network monitor / Winsock API calls tracer you should see: - A successful connect to proxy Server - A successful interchange of VER, CVR and USR commands, and a proxy disconnect - AN UNSUCCESSFUL CONNECTION ATTEMPT to (Proxy Address:80) when it should connect to (Proxy Address:8080), followed by the corresponding error message. 5 - If you change proxy address in both Proxy Server and Messenger to port 80 and it will work fine, but this is not the point. 6 - Another way to fool this bug is to add a second HTTP proxy Server on the local machine, configured on port 80. Eg: Internet <---> HTTP Proxy (on port 8080) <--intranet-> Local HTTP Proxy on port 80 <---> Messenger PS: This bugs affects MSN Messenger 5.0 and it seems to affect previous versions of Messenger also.

    T S 2 Replies Last reply
    0
    • G Gabriel 2

      Use proxy server Type: HTTP Proxy Server: Proxy Address Port: 8080 4 - Try to connect to the server. With a network monitor / Winsock API calls tracer you should see: - A successful connect to proxy Server - A successful interchange of VER, CVR and USR commands, and a proxy disconnect - AN UNSUCCESSFUL CONNECTION ATTEMPT to (Proxy Address:80) when it should connect to (Proxy Address:8080), followed by the corresponding error message. 5 - If you change proxy address in both Proxy Server and Messenger to port 80 and it will work fine, but this is not the point. 6 - Another way to fool this bug is to add a second HTTP proxy Server on the local machine, configured on port 80. Eg: Internet <---> HTTP Proxy (on port 8080) <--intranet-> Local HTTP Proxy on port 80 <---> Messenger PS: This bugs affects MSN Messenger 5.0 and it seems to affect previous versions of Messenger also.

      T Offline
      T Offline
      Todd C Wilson
      wrote on last edited by
      #2

      Gabriel 2 wrote: Install MSN Messenger Well that's the bug, right there. You should be using email.


      "I was in a computer game. Funny as hell, it was the most horrible thing I could think of."

      G 1 Reply Last reply
      0
      • G Gabriel 2

        Use proxy server Type: HTTP Proxy Server: Proxy Address Port: 8080 4 - Try to connect to the server. With a network monitor / Winsock API calls tracer you should see: - A successful connect to proxy Server - A successful interchange of VER, CVR and USR commands, and a proxy disconnect - AN UNSUCCESSFUL CONNECTION ATTEMPT to (Proxy Address:80) when it should connect to (Proxy Address:8080), followed by the corresponding error message. 5 - If you change proxy address in both Proxy Server and Messenger to port 80 and it will work fine, but this is not the point. 6 - Another way to fool this bug is to add a second HTTP proxy Server on the local machine, configured on port 80. Eg: Internet <---> HTTP Proxy (on port 8080) <--intranet-> Local HTTP Proxy on port 80 <---> Messenger PS: This bugs affects MSN Messenger 5.0 and it seems to affect previous versions of Messenger also.

        S Offline
        S Offline
        Shog9 0
        wrote on last edited by
        #3

        If only that were the only bug with MSN Messenger and HTTP proxies... :( Things that currently prevent me from using Messenger: 1) HTTP proxy requires NTLM authentication 2) Messenger doesn't like this. 3) Messenger also doesn't like the local proxy set up to convert basic authentication to NTLM authentication. 4) Messenger sucks. ---

        But, oh god / Under the weight of life / Things seem / Brighter on the other side - David Matthews, Big Eyed Fish

        1 Reply Last reply
        0
        • T Todd C Wilson

          Gabriel 2 wrote: Install MSN Messenger Well that's the bug, right there. You should be using email.


          "I was in a computer game. Funny as hell, it was the most horrible thing I could think of."

          G Offline
          G Offline
          Gabriel 2
          wrote on last edited by
          #4

          Yeap, that may be the solution. Unfortunately, I'm getting used to it, and to have something telling me when a mail is received.

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups