Title: | Microsoft Exchange Server |
Notice: | |
Moderator: | FLASK2::SYSTEM |
Created: | Fri Feb 17 1995 |
Last Modified: | Thu Jun 05 1997 |
Last Successful Update: | Thu Jun 05 1997 |
Number of topics: | 1099 |
Total number of notes: | 5174 |
My costumer are using Windows 3.1 with remote boot on disk-less PC's in a NT-domain environment with one Exchange Server. They have just installed the Exchange Client (setup /n) - and it won't work. The errors comes in two steps when the Exchange Client is activated: 1) When the Exchange Client is started it is required to logon to the domain - which already has been done in DOS before entering Windows. 2) After entering user/password again the reply is " Server unavailable ...do you want to retry or work off-line...maybe there are not enough system resources". The environment are as follows: - Server and client are connected via LAN. Server site: - NT-server ver. 3.51 SP5 on Intel platform. - Exchange ver 4.0 SP2 (can't use SP3 while they are using remote backup) Client site: - LANmanager ver. 2.2C.0 (for remote boot) using Netbios over NetBEUI (no TCP/IP !) logon takes place in DOS before Windows is started. - Windows 3.1 - Microsoft Network (or 100% compatible) for the networkpart i Windows. - Exchange Client ver. 4.0.994.56 Following test has been done: - RCPping test from client (Windows version) over "ncacn_nb_nb" between Server and Client is OK. - Connect to specific file-share on Exchange Server from client works OK. - Before We start Windows We tried to start Exchange Client for DOS - it works OK. - We installed Windows 3.1 + LANmanager ver. 2.1 on a PC with local harddisk. It works OK. As I see the problem is the LANmanager/Windows setup when using remote boot facilities. My problem is to find something like an SPD for the Exchange Client or "Requirements for Microsoft Exchange Client Installation", when using remote boot with Windows 3.1. Any ideas ?
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
870.1 | Support specialist | NETRIX::"[email protected]" | Helge Damsholt | Fri Feb 14 1997 09:32 | 9 |
Hi. Problem at this customer have been solved by changing msnet.drv to lanman21.drv in windows, reinstalling exchange client. Best regards Helge Damsholt / digital Denmark [Posted by WWW Notes gateway] |