| 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 |
I'm at the NT Wizards this weel in Seattle and experiencing problems
working with my Exchange Server in Kanata Canada.
I'm dialed in over a local PPP port in SEO. I can start Exchange,
answer all prompts and passwords for Exchange and MAPI for ALL-IN-1. I
then see the Exchange window with messages listed but never get
control. The task manager shows Exchange is not responding.
I have no problem with Teamlinks except for speed.
I'm 8 hops away from KAOEXC1 and wonder if there is a registry entry I
need adjust for network delay.
Thanks
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 914.1 | OTOOA::seosrv1.seo.dec.com::naish | OO4ME Paul Naish DTN 631-7280 | Tue Mar 04 1997 07:11 | 5 | |
Solved it. I had to set the DNS and WIN Server addresses for the local office. Weird behavior. It stated up, verified the login then stalled. | |||||
| 914.2 | OGOPW1::tunsrv2-tunnel.imc.das.dec.com::michaelw | [email protected] | Tue Apr 15 1997 00:00 | 24 | |
... and anytime you need to do Windows Networking to some machine that is not in Wins or doesn't play well... put it in C:\WINDOWS\LMHOSTS. as <ip num> <short name> <fqdn name> #PRE (Tip: search your machine, Win95 or WinNT, for a file called LMHOSTS.SAM. Put in your entries, then save as LMHOSTS. with no extension on the filename) The #PRE tells Windows Networking to "pre-load" the Windows Networking NetBIOS name table cache at the startup of the network software. It will never have to resolve this name. I use it for some Alphas running NT that aren't resolved via WINS, but I still want to reach their drive shares. Same goes for Exchange. [email protected] Tal. | |||||