Still don't have a fix for MSN

[Keith Judkins]

Deleted MSN, rebooted, re-added the account and now we are back to the same
original issue.

Keith Judkins
IT (Sharon's Helper)
VT Milcom
   A Business Unit of VT Group
3185 Industry Drive
North Charleston, SC 29418
(843) 767-1442 x72244 Office 
(843) 813-8335 Cell 
www.vtmilcom.com   

VT Milcom is: "Passionate about PEOPLE, PARTNERING and PERFORMANCE!"
________________________________________
Attention:  The information contained in this message and or attachments is
intended only for the person or entity to which it is addressed and may
contain business sensitive and/or privileged material.  Any review,
retransmission, dissemination or other use of, or taking of any action in
reliance upon, this information by persons or entities other than the
intended recipient is prohibited. If you received this in error, please
contact the sender and delete the material from any system and destroy any
copies.
________________________________________

-----Original Message-----
From: daniel.atallah at gmail.com [mailto:daniel.atallah at gmail.com] On Behalf
Of Daniel Atallah
Sent: Monday, December 07, 2009 12:28 PM
To: Keith Judkins
Cc: support at pidgin.im
Subject: Re: Still don't have a fix for MSN

On Mon, Dec 7, 2009 at 12:24, Keith Judkins <keith.judkins at vt-group.com>
wrote:
> Ok, I did that. Now I am getting a different error. The first time the
HTTP
> server name block was blank. The second time you can see it put an addy in
> the block automatically. In an earlier email I attached the log from the
MSN
> client that is connecting perfectly. Can anything be used from it to
correct
> this issue?


Your MSN account appears to be messed up, it is trying to connect to a
blank server name and you've changed various port settings
incorrectly.

Try to delete it and re-add it.

-D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: purple-debugDec709_5.log
Type: application/octet-stream
Size: 22466 bytes
Desc: not available
URL: <http://pidgin.im/pipermail/support/attachments/20091207/f77eeac8/attachment-0002.obj>