Connecting to Exchange

Posted on 2004-04-06
Medium Priority
Last Modified: 2010-04-08
Having problems with one system connecting outlook 2000 to Exchange 5.5.  Originally the system had windows 98 on it with the same issue and now has Windows XP.  I can check name and it picks it up immediatley but when I launch outlook it takes 5 to 10 minutes to connect and times out a couple of times, but eventually does connect.  I have reformatted and reloaded office 2000 and still have the same thing.  At this time thought there was something wrong with the server.  I went to another system and logged in to the domain with the problem user and launched outlook and connected without issues.  I am at a loss as to what the problem could be please help.
Question by:sweetom
  • 3
  • 2
  • 2
LVL 67

Expert Comment

ID: 10768207
What OS?

You might try resetting your TCP/IP stack:
 Click Start->Run->CMD <enter>
 at the prompt, type:

 netsh int ip reset > c:\resetlog.txt <enter>

Netsh references:

To reset your windows sockets, download and run the following:

 Manual method can be accomplished by deleting the following two keys in the registry:
 and then reboot


Author Comment

ID: 10769282
OS? as I said Windows XP.  TCP/IP works for everything else why would it be giving me issues with Outlook connecting to Exchange?  System logs into domain and all other applications work fine.  I am not at the site at this point, and this doesn't seem to address my problem, or at least I don't understand how this would help.  The system is directly on the same LAN.  I have connected with outlook express as an short term solution, but would really like to understand what has happened.  I have created another user and it works everywhere else except this system as does the user in question.  but neither userworks at this workstation.  I have reformatted this system and reinstalled office and I have the same issues.  
LVL 67

Expert Comment

ID: 10770418
I'd be inclined to think hardware issue.
Check/replace the NIC - change cables - try a different network drop/port on the hub/switch.
If it was there with 98 and now with a new OS  - it's gotta be the device...
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!


Accepted Solution

GearyTech earned 500 total points
ID: 10780493
I agree with sirbounty. Is it possible this PC is connected to a different switch than the other PC's? You could try adding the Exchange server name to the hosts file... also check the PC to be sure the DNS entry in TCPIP is the same as the rest of your network (maybe pointing at the router instead of the server?) What are the response times when you ping the Exchange server (any different from the rest of the network?)

Good luck!

Author Comment

ID: 10806953
Ok, so the original system had hard drive issues and it seems other issues as well.  So the hardware was swapped out with another comparible system none of the hardware from the original was used.  Still have the same issue when formating with XP and installing Office 2000 using Outlook to connect again finds the name and when launching outlook it times out.  When I connect with outlook on a different system it works fine. I have connected this system to the network outlet where I know it just worked, and it has the same issue.  I think the DNS issue might be the problem, but can anybody explain why this would be the problem?  Does it look for the FQDN or what? I thought I was looking for Netbios name.  And why when it checks for the name it finds that just fine?

Expert Comment

ID: 10807256
I believe it's netbios over TCP/IP... so, check your DNS settings in the TCP/IP stack and/or try putting the Netbios name & IP of the Exchange server in the hosts file on the workstation.

Author Comment

ID: 10809909
Thanks everyone,  mostly GearyTech.  The answer was the DNS and I added the server into the hosts file and everything worked.  This is a new job for me and did not how things were configured I definately know now.

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

MS Outlook undoubtedly is the most widely used email client.Its user-friendliness, cost effectiveness, and availability with Microsoft Office Suite make it the most popular email application.  Its compatibility with Microsoft applications like Exch…
As a matter of fact, Outlook OST files are of much importance in relation to Exchange mailbox. OST files are independent as they are simply copy of data of a user’s mailbox on Exchange Server. Though, if the server’s status is changed or it is dama…
The video provides a quick and easy steps to migrate MBOX file to well known Outlook PST and Office 365. Besides this, it also supports and migrates more than 20 email clients of MBOX which include AppleMail, Opera, Thunderbird and SeaMonkey effortl…
If you are looking for an automated tool which can generate reports for Outlook emails and other items from PST file, then you can go for Kernel PST Reporter tool. The reports which are created by this tool are helpful to analyze and understand PST …

627 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question