Vista - Unable to connect as of late last week...

Here is the connection log entries:

*********************************************************************************
*
* Log opened: 2009-05-04T18:40:17Z
*
*
* About this log file - MSNMsgr.txt
* Windows Live Messenger 14.0.8064.0206
*
* This log file is created on your computer when the Connection Logging
* setting is selected in the Options dialog box. You can turn off this
* setting at any time. To turn off this setting, click the Tools menu, and
then
* click Options. In the Connection section, click the Advanced Settings
button.
Under Windows Live Messenger Settings, clear the logging check box, and
* then click OK.
*
* Caution: This file may contain personal information. Anyone with access to
* your Windows desktop can see the contents of this file.
*
<SystemSettings><System SystemTime="05/04/2009 18:35:59 UTC"
WinsockVer="2.2" MsgrVersion="0xe001f80" WinInet="1.2" LCID="0x0409" /><OS
SuiteMaskProductType="0x1000001" MajorVersion="0x5" MinorVersion="0x1"
BuildNumber="0xa28" ServicePack="0x2" /><IESettings Version="7.0.5730.11"
UseSSL30="0x1" CheckCertRev="0x0" /><Connection Type="No proxy" Mode="0x0"
/></SystemSettings>
*********************************************************************************
[14:40:25.26] 0f24 Messenger: Zone_Net
CTCPNetworkLayer::Connect (01EC86A0) (100) >> connecting to
messenger.hotmail.com:1863
[14:40:25.26] 0f24 Messenger: Zone_Net
CConnTestDialog::OnConnectionStateChange recieved state change for id(100)
from 1 to 3
[14:40:25.28] 0f24 Messenger: Zone_Net
CTCPNetworkLayer::ResolveHost (01EC86A0) >> resolving messenger.hotmail.com
[14:40:25.29] 0a7c Messenger: Zone_Net
CAsyncGetAddrInfo::Run >> (0xbfff00) getaddrinfo succeeded for
messenger.hotmail.com, ticks 1, time 16ms
[14:40:25.29] 0f24 Messenger: Zone_Net
CConnTestDialog::OnConnectionStateChange recieved state change for id(100)
from 3 to 5
[14:40:25.29] 0f24 Messenger: Zone_Net
CTCPNetworkLayer::ConnectToIP (01EC86A0) (100) >> connecting to
207.46.96.153:1863
[14:40:25.29] 0f24 Messenger: Zone_Net
CTCPNetworkLayer::ConnectToIP (01EC86A0) (100) >> success 0x01ec86a0,
socket=2192, LastError=10035, WM(1056)
[14:40:26.18] 0f24 Messenger: Zone_Net
CTCPNetworkLayer::OnMessage (01EC86A0) (100) >> Got
WM_WSASELECT_MESSAGE(1056) from WSAAsyncSelect for socket = 2192, error =
10061, event = FD_CONNECT
[14:40:26.18] 0f24 Messenger: Zone_Net
CTCPNetworkLayer::OnError (01EC86A0) (100) >> called with 0x8007274d
[14:40:26.18] 0f24 Messenger: Zone_Net
CTCPNetworkLayer::OnSocketClose (01EC86A0) (100) closing socket 2192
[14:40:26.18] 0f24 Messenger: Zone_Net
CConnTestDialog::OnConnectionStateChange recieved state change for id(100)
from 5 to 1
[14:40:27.37] 0f24 Messenger: Zone_Net
CTCPNetworkLayer:isconnect:01EC86A0. m_sock == 4294967295
[14:40:27.37] 0f24 Messenger: Zone_Net
CConnTestDialog::OnConnectionStateChange recieved state change for id(100)
from 1 to 1
[14:40:27.91] 0f24 Messenger: Zone_Net
CConnTestDialog::OnConnectionStateChange recieved state change for id(103)
from 1 to 5
[14:40:27.93] 0f24 Messenger: Zone_Net
CConnTestDialog::OnConnectionStateChange recieved state change for id(103)
from 5 to 8
[14:40:27.93] 0f24 Messenger: Zone_Net
CHTTPNetworkLayer::SendHttpDataInternal@xxxxxx: (103) >> Posted to URL (26
bytes), hr = 0x0
http://messenger.hotmail.com/gateway...er.hotmail.com
[14:41:30.08] 0f24 Messenger: Zone_Net
CHTTPNetworkLayer::HttpCallback: (103) >> called back with 0 (HTTP:504)

One other thing to note, we block access out our firewall and require users
to go through a proxy. That proxy address is 10.240.4.73 and from what i see
in that log and from wireshark captures i took, Messenger is not using the
proxy settings and is trying to directly access the IP address
207.46.96.153...

This behavior started late last week. Anyone else?

Also running the Windows LIve Messenger Connection Troubleshooter fails on
Key Ports... Although it doesnt tell me what ports are required. The verbage
is:

Failed to connect to the service. This could be due to improper proxy or
firewall settings. Please review your proxy and firewall settings. Proxy
settings can be accessed through Windows Live Messenger Options. For Firewall
settings, please see the retailer's instructions.

I maintain the firewalls and proxies. Can someone elaborate on what ports
are required?

As said before this worked through our proxies and firewalls up until late
last week.

Greetings,

The ports used are 1863, 80, and 443.

However, given it's not hitting your proxies, it would make sense that these wouldn't be
connectable.

What kind of proxy are you using? Are you absolutely sure the proxy server is setup and
usable in IE?

--
Jonathan Kay
Microsoft MVP - Windows Live Messenger
MSN Messenger/Windows Messenger
MessengerGeek Blog: http://www.messengergeek.com
Messenger Resources: http://messenger.jonathankay.com
(c) 2009 Jonathan Kay - If redistributing, you must include this signature or citation
--

"n8vtexan" <n8vtexan@xxxxxx> wrote in message
news:5C46EAF3-18A2-4E12-9E30-EAE88B06E18B@xxxxxx

Thanks Jonathan, The proxie server we use is a combination of 6 ISA servers
in an array for authentication and 2 ContentKeeper devices for content
filtering.

This system has been in place for over a year now, coming up on two. IM was
working as of last week.

One thing i noticed in the test log was that it says:

Connection Type="No proxy" Mode="0x0"

I verified that it pulled the IE proxy settings and i entered my
credentials. However the trace shows the traffic trying to directly connect
to the IP address in one of my last posts, which of course the firewall is
not going to allow. Also it is trying to get out on port 1209 i believe. If
you want i can run another capture and forward along. At this point any help
would be greatly appreciated.

Thanks,

Shane


"Jonathan Kay [MVP]" wrote: