Conference 7.286::macintosh

    

    Hmmm... This is strange.  I can use the Exchange Client for Mac 
    here at work no problem.  But from home, dialed up through FreePPP
    and TCP/IP, I get the "not enough resources" error when I try to 
    connect.  All my other TCP applications work fine from home and I
    can ping the Exchange server no problem.
    
    If it's DNS vs. WINS, why would it work at work and not at home,
    using the same DNS servers and the same Exchange server?  I also
    tried it using the traditional MacPP software and got the same error,
    so I'm not sure it's related to OpenTransport.  I actually updated to
    Open Transport at home thinking it might fix the problem.  (Silly me.)
    
    I've been using the SP2 Mac Client.  Tonight (or later this week) I'll
    try the SP3 Mac client mentioned here.
    
    To me, the problem seems like a local Mac problem since the connection
    works for only a split second before giving up.  It's not like it's
    trying to resolve the name for a period of time.  Instead, it seems to
    find a problem immediately--which would point to a conflict of some
    sort on the local system folder, but I can't find any so far...
    
    Peter
    

Peter,
I have not tried again Exchange since I've inserted my note. In my case, I have 
really plenty of CPU (Perf 6400 @200 Mhz), real RAM (48 Mb) and disk space (~500 Mb free)
I am interested in helping in the debugging of this case. Next week, I am
at a 13-hour flight distance away from my macintosh now.
Jean-Pierre.

    I asked the MIS folks here at NQO if I had to use
    messy Exchange. Why couldn't I use another mail program
    that supports SMTP protocol? To my surprise, they agreed
    to let me use Eudora instead of Exchange. Eudora is far
    better that PATHWORKS' Mail for Macintosh, so I am looking
    forward to it.

    So what are the advantages of Exchange over Eudora?
    Will I be missing something?

    Regards,
    Bob Anderson

>    So what are the advantages of Exchange over Eudora?
>    Will I be missing something?

The Exchange client (or a client that supports full MAPI) 
is required if you want to read and send mail using the 
Microsoft Exchange Server software.  

I don't think Eudora can work with the Exchange server, 
can it?

Instead, Eudora--like many other Internet mail clients
such as Netscape Mail or Claris Emailer--works with any 
POP3 server (for receiving and retrieving Internet mail) 
or SMTP server (for sending Internet mail).

The Exchange client doesn't support POP3 or SMTP servers.  
It is designed to work only with the Microsoft Exchange 
Server.

As for other full MAPI clients that can work with the 
Exchange server, our own TeamLinks for Windows will soon
work as such a client (it's going to Field Test with that
capability in a couple of weeks), but the TeamLinks for 
Macintosh client is a little behind the feature curve 
right now.

I'd be curious if and when there are some other choices
of full MAPI clients to work with the Exchange Server, 
but right now, especially on the Mac side, I believe the 
Exchange Client itself is our only choice.

Peter

Okay, last night I installed the Service Pack 3 Mac client and I 
got the same "not enough system resources" error when I tried to 
connect via FreePPP and OpenTransport V1.1.2.

I just re-read some of the notes in this string and it sounds like
this *is* working for some folks.  So why are some of us getting 
this error when trying to dial-in over PPP?

To recap, I can connect to our Exchange server with my Mac at work
with no problems.  All my other TCP/IP applications are working fine 
from home over PPP.  I can ping our Exchange server from home over
PPP.  But the Exchange Client won't connect to the server.

Any thoughts on what I might do to troubleshoot this further?

My last thought is maybe it's a Power Mac vs. 040 Mac problem.
My Mac at work is a Power Mac and my machine at home is an 040 
machine.

Frustrated,

Peter

I just got an answer to my question about the resource error in the 
comp.sys.mac.comm newsgroup.  Sounds like even when you're using TCP/IP, 
AppleTalk *must* be turned on.  That would explain why I can connect at
work no problem--AppleTalk is always turn on here at work so I can use
AppleShare.  At home, I keep AppleTalk turned off.

I'll try it tonight and report back.  Supposedly, there's a system extension
that comes with Open Transport 1.1.1 and 1.1.2 called Remote Only.  This 
extension lets you turn on AppleTalk without using your modem port or
printer port. 

The newsgroup reply also says this problem will be fixed in a future release
of the Exchange Mac client.

It'd be really nice if this fixed the problem...  Wish me luck.

Peter

Keeping Appletalk activated made it!!!
I can read my mails from home now!

    
    Jean-Pierre beat me to it.  Indeed, turning on AppleTalk fixes the
    problem.  We Mac users can still work from home even if Digital
    switches to Exchange.  A small comfort, but I'll take it.
    
    My heart will always be with ALL-IN-1 and TeamLinks for Mac, but if
    we have no choice, at least I still have my Macintosh!
    
    Peter

I have not yet read all of this topic. So I hope I haven't missed something.

Well I think is is ust great that MS Exchange works on MacOS :( (NOT) but what
are your thoughts on the exchange of PPP (RAMS) for RAS only?

	Here, and I assume every where else in decland the decheads in IPS
and what every else they call the group responsible for exchange rollout
have told us that the normal PPP (RAMS) will be retired very soon for a RAS only
dial in. Also they have check the MS only box on authentication so unless
MAC's PPP allows this then your out in the cold. Any one that say Microsoft
and intergration in the same breath should be taken out and given a new set
of eyes, ears and probably a brain! 

	I have nearly got PPP 2.3 going on Digital UNIX which will do the ms
specific stuff and dial into RAS.

	So tell me, is this what is happening else where in Digital RAMS -> RAS
and if so has any one got source code for PPP that works with OT so that it can
be broken to work with RAS?


	Cheers
		Mark :)

The callback of RAS does not seem to work against macs, I don't know why but
the straight connection works. 
I had some big trouble with the connections tools these last days, but I already
tried a connection with a DHCP server providing dynamically the IP address and
it worked. 
After the solution of the Exchange issue, maybe I should try RAS again, just in
case the Appletalk magic works for the callback too ;-) 

Okay.  These last two replies were pretty confusing.  Can someone
restate them in English?

After re-reading them both a couple of times, it sounds like 
the dial-in connections all through Digital are changing sometime
soon from "RAMS" to "RAS" (whatever that means).  Beyond that, 
we've got two different opinions on whether that will affect people 
(like me) using Macs to dial in via PPP.

Anyone out there who can clarify?

Peter

RAS stands for Remote Access Service and is the PPP server that comes with
Windows/NT. This server is of course Wintel oriented and includes a callback
feature. Unlike ACB which always requires a pre-registration of the phone number to
be called back, RAS can either have the same registration or allow the user to
specify the number at connection time.
In either mode, I can't have RAS call me back, in the second case because I
get no dialog that would let me indicate that number.
I am not familiar with RAMS, sorry for the confusion.

Re .40

> We Mac users can still work from home even if Digital
> switches to Exchange.  
    
Its not Exchange that's the problem, rather the use of propietary PPP
authentication.

> Here, and I assume every where else in decland the decheads in IPS
> and what every else they call the group responsible for exchange rollout
> have told us that the normal PPP (RAMS) will be retired very soon for a RAS only
> dial in. Also they have check the MS only box on authentication so unless
> MAC's PPP allows this then your out in the cold. 

Yes,  we're out in the cold.  Here in ZUO (Switzerland) the only dial-in
service will be Windows NT RAS using "Microsoft encrypted authentication", 
by order.  No clients  except W95 and WinNT.  See
<http://www.microsoft.com/kb/articles/q136/6/34.htm> for RAS authentication
tech info.  The PPP modem pools that used to allow access by Macs are being
withdrawn (so I'm told by the network guys).  

However, SofWindows 95 does work with RAS but is painfully slow on my
Quadra 650 with PPC card.  I expect to have a hard PC real soon now.   :-(

Steve.