Chris,
Interesting post. Thanks!
Mark
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Bradfield,
Chris
Sent: Tuesday, March 27, 2001 11:54 AM
To: '[EMAIL PROTECTED]'
Cc: '[EMAIL PROTECTED]'
Subject: RE: [Win4Lin-users] What about Win4Lin v2.1?
FYI, I have Outlook talking to Exchange just fine under
Win4Lin 2.0. Outlook is perfectly happy using TCP/IP
only to communicate. The trick is convincing it to do
so instead of using another protocol.
I had to do two things:
1 - Fool Win4Lin into thinking that full windows networking was
installed.
2 - Tell Outlook to use TCP/IP only for connecting to the Exchange
server.
Step 1:
Open Network properties from the Control Panel.
Click Add, Protocol, Microsoft, TCP/IP.
Click Cancel when prompted for an adapter.
Click OK and ignore the "Your network is not complete" message.
Setup will copy some files from the Windows CD and ask you to
reboot - you don't have to.
Note - I found this one by accident when I first installed Win4Lin
on a test system. <sheepish>I didn't RTFM and started configuring
networking like I would a normal Win98 machine.</sheepish> However,
I have duplicated the procedure on two other Win4Lin installs, so
I know it works. Outlook is my main reason for running Win4Lin...
Step 2:
Edit the registry and look for this key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\Exchange Provider
The key you need to change is "Rpc_Binding_Order"
The default setting is
"ncalrpc,ncacn_ip_tcp,ncacn_spx,ncacn_np,netbios,ncacn_vns_spp".
Delete all these but "ncacn_ip_tcp".
Restart Windows and when you configure the exchange server in Outlook,
specify it by IP address *not* by computer name.
Note - This is also a good trick for speeding up your connection if you're
using a dialup to connect to your Exchange server.
Good luck!
Chris
> -----Original Message-----
> From: Lyndon Van Wagner [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 27, 2001 7:38 AM
> To: [EMAIL PROTECTED]
> Subject: [Win4Lin-users] What about Win4Lin v2.1?
>
>
>
> Hi. I'm a new user to Win4Lin, and like it alot.
> It seems everyone is talking about Win4Lin v3.0, but I'm
> waiting for v2.1,
> which is supposed to have MS Client Networking emulation as well.
> (Is this VNET, and does it really require a new IPaddr for
> the Windows
> session?) I need this so my Outlook98 can talk to a MS
> Exchange Mail Server
> without using POP3/IMAP. Has anyone heard when this is
> supposed to be
> available?
>
> --Lyndon
>
>
> ===========================================================
> Lyndon C. Van Wagner Senior Systems Engineer
> ===========================================================
> West Group, 50 East Broad Street, Rochester NY 14694
> TEL:716.546.5530 ext 3523 FAX:716.327.2662
> WORK EMAIL:[EMAIL PROTECTED]
> HOME EMAIL:[EMAIL PROTECTED]
> -OR- [EMAIL PROTECTED]
> -OR- [EMAIL PROTECTED]
> ===========================================================
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
> _______________________________________________
> Win4Lin-users mailing list
> [EMAIL PROTECTED]
> https://lists.netraverse.com/mailman/listinfo/win4lin-users
>
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
