bigwong
asked on
outlook client cannot conect to exchange
Please help the captioned subject.
My environment:
Outlook 2003 in Windows Server 2003 running terminal services
Suddenly newly created mailbox cannot connect to Exchange Server 2003 but those mailboxed created before worked properly.
I tried the same mailbox in other computer, it worked, so should be the problem of this Terminal Server in Windows Server 2003. But what's the problem?
My environment:
Outlook 2003 in Windows Server 2003 running terminal services
Suddenly newly created mailbox cannot connect to Exchange Server 2003 but those mailboxed created before worked properly.
I tried the same mailbox in other computer, it worked, so should be the problem of this Terminal Server in Windows Server 2003. But what's the problem?
R. Andrew Koffron
what's the error and when do you see it?
ASKER
When I create the outlook profile and click button <checkname>, it will show the error below after several seconds.
'Outlook could not log on. Check to make sure you are connected to the network and are using the proper server and mailbox name. The connection to the Microsoft Exchange server is unavailable. Outlook must be online or connected to complete this action'
'Outlook could not log on. Check to make sure you are connected to the network and are using the proper server and mailbox name. The connection to the Microsoft Exchange server is unavailable. Outlook must be online or connected to complete this action'
I'd double check memberships for the user, make sure there isn't any deny set on any of the groups. and probably delete the user account from the term server.
if it's just the one account it's quite strange, and either security groups, or a corrupt profile are my initial thoughts.
if it's just the one account it's quite strange, and either security groups, or a corrupt profile are my initial thoughts.
ASKER
I had tried delete this user from AD and recreate it, and also tried delete this user profile in this terminal server, but no luck.
I don't think it is the security group problem because there are other members they work well in this server. I think it is just the initial connection problem because once the other users work well in this server as the profile I had created before.
I don't think it is the security group problem because there are other members they work well in this server. I think it is just the initial connection problem because once the other users work well in this server as the profile I had created before.
is the AD intagrated DNS server set as the first DNS in the terminal server's tcp/ip settings?
ASKER
Yes
check if windows firewall service on ur terminal server is disabled. Also, u said old mailboxes u are able to access?
If yes, I would try to recreate a profile of a working user and see what happens.
If this doesnt work, then yes, there is aproblem with GC connectivity for this terminal server.
If this works, then I would like to know if these working and non working mailboxes are on different server? or same server?
If yes, I would try to recreate a profile of a working user and see what happens.
If this doesnt work, then yes, there is aproblem with GC connectivity for this terminal server.
If this works, then I would like to know if these working and non working mailboxes are on different server? or same server?
ASKER
I had disabled the firewall service and the old mailboxes are able to access in the same server.
I also tried to recreate a profile for old mailbox and it didn't work. I think it's GC conectivity prblem for the termainl server.
I also tried to recreate a profile for old mailbox and it didn't work. I think it's GC conectivity prblem for the termainl server.
correct! Please run DCDIAG on that terminal server.
ASKER
run dcdiag /s:dc
all pass except failed frsevent.
all pass except failed frsevent.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.