Windows Forum

Ask something
Discussion Locked

Outlook2000-Exchange connection problem

0 helpful
24 replies

by shafferm

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are using Exchange Server 5.5 running on our NT 4.0 Server. Outlook 2000 takes about 1 minute to load after clicking the shortcut on a Windows NT 4.0 Workstation. It takes longer on a Windows 98 workstation and less time on a Windows 2000 workstation. In order to get it to load that fast, we had to change the RPC_Binding_Order by moving ncacn_np to first in the list on each workstation in HKEY_LOCAL_MACHINE, Software, Microsoft, Exchange, Exchange Provider. Sometimes Outlook fails with the message "Network problems are preventing connection to the Microsoft Exchange Server computer." How can we correct this problem?

24 replies

by haig

Sounds like you're on the right track.
I'm assuming TCP/IP is your only protocol.

Find a test system and go back to the abovementioned registry location.
Set the value to ncacn_ip_tcp
Reboot and measure the result.
If you're pleased, implement on other machines.

This key tells outlook what protocols to use to locate an exchange server. If you follow these instructions, you're telling it to use TCP/IP only. In my experience, this can really speed things up.

by haig

Sounds like you're on the right track.
I'm assuming TCP/IP is your only protocol.

Find a test system and go back to the abovementioned registry location.
Set the value to ncacn_ip_tcp
Reboot and measure the result.
If you're pleased, implement on other machines.

This key tells outlook what protocols to use to locate an exchange server. If you follow these instructions, you're telling it to use TCP/IP only. In my experience, this can really speed things up.

by haig

Sounds like you're on the right track.
I'm assuming TCP/IP is your only protocol.

Find a test system and go back to the abovementioned registry location.
Set the value to ncacn_ip_tcp
Reboot and measure the result.
If you're pleased, implement on other machines.

This key tells outlook what protocols to use to locate an exchange server. If you follow these instructions, you're telling it to use TCP/IP only. In my experience, this can really speed things up.

by haig

Sounds like you're on the right track.
I'm assuming TCP/IP is your only protocol.

Find a test system and go back to the abovementioned registry location.
Set the value to ncacn_ip_tcp
Fire up Outlook and measure the result.
If you're pleased,implement on other machines.

This key tells outlook what protocols to use to locate an exchange server. If you follow these instructions, you're telling it to use TCP/IP only. In my experience, this can really speed things up.

by haig

Sounds like you're on the right track.
I'm assuming TCP/IP is your only protocol.

Find a test system and go back to the abovementioned registry location.
Set the value to ncacn_ip_tcp
Fire up Outlook and measure the result.
If you're pleased,implement on other machines.

This key tells outlook what protocols to use to locate an exchange server. If you follow these instructions, you're telling it to use TCP/IP only. In my experience, this can really speed things up.

by haig

Sorry about the _5_ replies :-)

They're almost identical.

The thechrepublic server didn't seem to accept the first, so I hit 'Submit' a couple of times. :-)

by Former member

What is the ping time? What is the ping time for names? What is between your PCs and the server? Routers, switches, WAN? more info pleez...

by kenalmoore

I had a problem very simular to this. First try ping and nbtstat -a from the workstation or win98 clients using the Exchange Server netbios name andor ip address. If no response, you have a WINS problem. It could be that your clients and Exchange server are not registered in the WINS database. Please let me know if this works.
Advice: upgrade your Outlook 2000 to SR1, there is a few patches that help with the SR1 from Microsoft. Check the Microsoft Update for Office patches too.

by mcarswell

I am not exactly sure why this is but some time the outlook profile has issues nowing what server it needs to connect to and i have seen this more with roming profiles where the exchange profile is kept in the users Profile so that it will travel with the user to what ever computer they log in to. If you go under the exchange server properties under the users profile and do a checkname this usally will fix this issiue you also may have to delete the exchange service and re add them.

by nagazaki

I already had such a problem, and I resolved it by simply add the IP and the exchange server's name in the hosts file (location : winnt\system32\drivers\etc\ ).
It's quite simple to do and very efficient.

Don't forget to reboot the computer after modification.

Hope it helps,

NaGaZaKi

by frobo

Hi there,

there a cuple of things to deal with.
1st- Outlook is connecting via RPC to the Exchange Server, look with RPC-Ping for time relevant connection problems. But i mean you don?t have problems there.
2sc- If you are using WINS and DNS for name resolution, Outlook takes allways DNS to find the Exchange Server IP-Adress. This is solved very differnt in NT, W2k and W9x, the qualtiy of the IP-Stack is in W2k and NT much higher then in win9x.
Speed it up with editing the HOST file like the Anwser9 is offering, this will work fine.

by frobo

PS: For changing a HOST or LMHOST file you don?t need realy to reboot ! Just take
NBTSTAT -RR to flush the netbios names Cache table (and if you want make an PING to the Server Name).

This discussion is closed to new replies.