• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 305
  • Last Modified:

Oulook 2003 always starts offline

I have a customer running SBS 2003 and 30 workstations (a mix of XP and Windows 7).

One user on the network is experiencing issues on her XP machine in that each time she opens Outlook, it is Offline. She can disable the "Work Offline" option and Outlook works as normal UNTIL she closes it and re-opens.

If I try and create a new Outlook profile, when I put in the Exchange Server name and her name then choose the "Check Names" button, I get a message saying that the operation could not be completed as the connection is not online (or words to that effect).

On her existing profile, if I turn off cached mode then the set of folders cannot be opened.

She can ping the server both by name and IP address. There are no rogue entries in the HOSTS file.

She has full admin rights on her own PC.

If I log on to her PC as another user, then I can create a new Outlook profile no bother.

PC is fully up to date as far as service packs and Windows updates are concerned.

I don't really want to have to re-create her full user profile on the PC unless it is THE last resort.
Chris Millard
Chris Millard
1 Solution
If you use a DHCP to assign the client network addresses, could you verify that the correct ones are provided?
Try to assign the IP and DNS manually.
I assume the user machine has only one card .. if not check the binding order of the NICs
Also, you could check for a "rogue" NIC in the registry :
if you see an adspter that you dont recognise then just delete it.
Haresh NikumbhSr. Tech leadCommented:
have you refer below link .. same question was asked and it solved by configuring new profile

Chris MillardAuthor Commented:
@takecoffee - as stated above, I cannot create a new mail profile as I cannot resolve the names

@sirakov - I can confirm the the IP address details are correct, the PC has only one NIC and there are no rogue reg entries. This appears to have happened for no apparent reason. There are no event log entries that relate to the problem or any other networking problems for that matter.
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Still it seems to be a dns issue
You could create a new Outlook profile if you type the IP instead of the name of the ex server ... but it wont solve the issue.
Could you run >ipconfig /flushdns on the client and on the server
As workaround and to prove a dns issue, try adding the
Exchange server into the host file (both netbios name and FQDN of the server)
Do you have another DC except the SBS ?
Are there any proxy on the clients ?
How about "nbtstat -A <exchange server IP>" from the client ? (Dou you see several names listed?)
Can you access the mailbox through OWA ?

IF the user can acces his mailbox OK from another machine, then as a last ressort you could delete his profile and re-add it to the domain.
Chris MillardAuthor Commented:
I can't try anything now until the user goes home this evening, but I am not convinced that it's a DNS issue as it is affecting just this one user on the PC (other users work ok on here).

I can ping the server by IP and by NetBIOS name and FQDN. I already tried adding the names to HOSTS but it made no difference.

There are NO other DCs on the network at all, and no proxies.

User can access Email through OWA.
Nooo is no DNS.

I will suggest you to repair your office installation.

When you install the software and create a new user on the PC, office installs a set of files per user to be able to keep the user's settings within its container maybe if you reinstall this will go away.

Better than that, login with an Administrator user on the PC, rename the user's windows profile, re-create the user by logging in the user, copy any user files, connect user to exchange, wait for emails to finish download, grab the old .NK2 file from old profile (Outlook 2003, 2007 with Exchange 2003) and copy to new profile.

Don't waste to much time on getting the cause, you already know that recreating the windows profile will do it now find the fastest way to perform that task and problem solve.  :-)

Good Luck
Chris MillardAuthor Commented:
Creating a new Windows profile for the user fixed the issue.
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

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Tackle projects and never again get stuck behind a technical roadblock.
Join Now