Can't connect Outlook to Exchange

[BobSchleicher]

When I install outlook on the Exchange Server it connects but when I try to connect to the server from another workstation it is always asking for a username and password.

I can map a drive to c$ on the exchange server without any problems. It just won't let me connect Outlook.

Any ideas?

BobSchleicher

 

[Zelandakh]

What? Please explain more clearly what you have done and what you are trying to achieve.

 

[Zelandakh]

OK, I'm reading it again as it just doesn't make sense.
You've installed Outlook on an Exchange server? That's just plain daft and a massive security risk.

What do you mean it connects?

How have you configured Outlook on the workstation? Exchange or POP/SMTP?

 

[BobSchleicher]

It is in a test environment. I wouldn't install it on a production server. I only installed Outlook on it to rule out a variable.

When I opened Outlook for the first time on the exchange server (test environment) I confired it for the Exchange and it setup the account in Outlook with out any issues.

When I open Outlook for the first time at a workstation in the same test environment and configure Outlook for the Exchange server a login banner comes up (standard username and password banner when accessing resource that require a username and password) asking for the username and password. I enter the email account I am trying to add and that doesn't work so I use the Administrator account to connect and that doesn't work. If I try to map a drive to the Exchange Server from the same workstation it connects successfully.

Hope this is more descript.


BobSchleicher

 

[MitchellMTI]

Hi Bob-

Just for 100% clarity- the workstation experiencing the problem with Outlook connecting to Exchange is a member of the same domain as the Exchange server and logged in as a domain user setup with a mailbox, correct?

Which version of outlook?

Launch Outlook from the command line using the /rpcdiag switch (outlook.exe /rpcdiag) Does it show attempted connections to the Exchange server and a DC?

 

[BobSchleicher]

This is a valid member of the domain that can connect to the admin share on the exchange server without any issues.

Running rpcdiag only shows 1 line with a status of connecting. The dialog box asking for a username and password shows "connecting to testex0".

No matter what username or password I use I can't connect.

BobSchleicher

 

[Zelandakh]

Who are you logging on as on the Exchange server and the workstation (windows logon) and which accounts are you using to connect to Exchange within Outlook and does the one have permissions to connect to the other?

 

[BobSchleicher]

I have tried using Administrator and Test User both users have Domain admin rights. Web access works perfectly and both of these users logged into another workstation can map a drive to the exchange server successfully so rights shouldn't be an issue.

I was reading something somewhere that was mentioning a certificate (like ssl). Does this make any sense?

BobSchleicher

 

[Zelandakh]

Domain admin rights makes no difference. Mapped drives make no difference.

Certificate makes no difference.

No you log onto the workstation as domain admin and then connect to Outlook as the domain admin?

 

[BobSchleicher]

I try to connect to Exchange as the logged in user.


BobSchleicher

 

[Zelandakh]

OK, so OWA works fine - I assume it works fine on both server and workstation.

Dumb one - make the 2 accounts local admins on the workstation THEN configure the Outlook profile and click check name. Se if you get it underlined. Then start Outlook and see if it a restriction on the client set up that is throwing you.

 

[BobSchleicher]

The users are local admins everywhere and when I select check name the dialog box pops up asking for username and password.

BobSchleicher

 

[Zelandakh]

ok. Check for errors on your DNS or WINS servers - sounds like the client can't resolve the server name back to the Exchange server.

 

[BobSchleicher]

I don't have WINS installed but DNS checks out fine.
I will install WINS to rule out that scenario.

BobSchleicher

 

[BobSchleicher]

Installing WINS didn't change anything. I checked the Security logs and it shows the user connecting to TESTEX01 successfully so I am thinking it is Exchange Server wanting authentication.

I appreciate the help.


BobSchleicher

 

[Zelandakh]

If it lets you connect on the Exchange server and not the workstation, it shouldn't be Exchange auth.

Put entries into hosts and lmhosts files and restart the workstation. Confirm OWA works for both NETBIOS name and FQDN.

Is the workstation a Vista box?

 

[MitchellMTI]

Any chance this test domain has non-default group policy setting with regards to security?

Maybe a rsop.msc on the workstation to see what policies are applied to it?

 

[BobSchleicher]

I checked everything in rsop and it is just the default policy and nothing out of the ordinary.

This test environment is just a clean install of:

Windows 2003 ENT 180day trial
1 DC
1 Exchange (HUB, CAS, Mailbox)
1 Edge

1 Windows XP workstation

All in the same test domain with "Out of the box" setttings. I haven't changed any policies or anything.

I ran the same scenario using Ex2003 and everything works perfectly. I do a clean install of everything using Ex2007 and I can't connect my Outlook to the Exchange server. This is very frustrating.

BobSchleicher

 

[Zelandakh]

It may be frustrating but if this is straight vanilla stuff then you aren't going to be the only person struggling.

Ping server - response?
Ping server.domain.com - response?

Is it server.domain.local or not?

 

[BobSchleicher]

Everything is local.
I have successfully pinged the IP, Name, & FQDN of each to and from each.

TESTDC01 - 192.168.0.247 (Proliant ML330 G3)
TESTEX01 - 192.168.0.248 (Proliant ML330 G3)
TESTWS01 - 192.168.0.249 (HP/Compaq 7600)
100mb Switch - unmanaged

BobSchleicher