[ previous ] [ next ] [ threads ]
 From:  "Bosse Timothy" <Bosse dot tf at mellon dot com>
 To:  <m0n0wall at lists dot m0n0 dot ch>
 Subject:  FW: [m0n0wall] Windows Messenger for MS Exchange
 Date:  Mon, 23 Feb 2004 15:37:23 -0500
First of all, I am not quite sure this is a m0n0wall issue.  Perhaps you
might consider another discussion list dedicated to Windows Messenger

Secondly, do you allow people to use .net accounts in addition to
Exchange IM services?  Assuming that your exchange server is on your
local network, the only other option that might cause a problem is if
you allow .net contacts (check preferences for IM).  If they have any
.net or outside contacts, when the wireless side goes down, you will
lose the connection to the IM server located outside of your network,
thus the "lag."

-----Original Message-----
From: Brandon Holland [mailto:brandon at cookssaw dot com] 
Sent: Monday, February 23, 2004 9:03 AM
To: m0n0wall at lists dot m0n0 dot ch
Subject: [m0n0wall] Windows Messenger for MS Exchange

We have a wireless internet provider and use m0n0wall as a
router/firewall for them.  When the wireless network dies (on their end
for whatever reason) our Windows messenger becomes unresponsive.  It
doesn't completely freeze, if you give it enough time, it'll work, but
try to imagine Windows messenger on a 25mhz 486.  That is literally how
it acts.  As soon as WAN comes back up however problem is solved.
We're not using .Net Passport, just MS exchange's "local" service, so it
shouldn't need the internet.  Why exactly is it even caring that the
internet is not up?
I'm completely bewildered.
Brandon Holland    (Brandon at Cookssaw dot com)
Network Administrator
Cooks Saw MFG, LLC ( <http://www.cookssaw.com/> www.CooksSaw.com)
    "Leading the bandsaw Industry
         by providing tomorrow's innovation today"
160 Ken Lane
Newton, AL 36352  (Click
en+ln&zip=36352&country=us&zoom=5>  for map)
   Ph: 1-800-473-4804    [ (334) 692-5074 ]
   Fax: (334) 692-3704