Hmmmmm I had been running PyMSNt for years with the same config on my own box and the box at work. Both had been running with actually no <host> flag at all but an <ip> flag which was 127.0.0.1. I was on vacation and one day it broke, possibly the CVR0 issue, it was basically the exact same time. But the fix didn't work. I don't see why the program needs to know the IP address to use for that, the OS should take care of that for it, and it worked fine for years prior to this.
I don't know that this has been settled. But it did fix my issue . On Aug 19, 4:29 am, Andrew Robert Gordon Henry Naylor <[EMAIL PROTECTED]> wrote: > Yes that fixed it, thanks for your help, I don't know why I put the > loopback address in that field, I was getting quite tired by that > point I guess. Thanks for referencing the diff changes, very interesting > > Sent from my iPhone > > On 19 Aug 2008, at 12:09, "Norman Rasmussen" <[EMAIL PROTECTED]> > wrote: > > > On Tue, Aug 19, 2008 at 12:59 PM, Andrew Robert Gordon Henry Naylor <[EMAIL > > PROTECTED] > > > wrote: > > That is very strange as I used the exact same config on my old > > system and it worked perfectly, it may have been running a slightly > > older version but has pymsnt's handling of that option been changed > > recently? > > > for a defined meaning of > > recently:http://hg.sharesource.org/pymsnt/rev/2e458af9ed2a > > > -- > > - Norman Rasmussen > > - Email: [EMAIL PROTECTED] > > - Home page:http://norman.rasmussen.co.za/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "py-transports" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/py-transports?hl=en -~----------~----~----~----~------~----~------~--~---
