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

During migration from NT to AD one workstation will not allow access to the Exchange server.

As is usually the case with questions posed here, I have tried everything I can think of to get around this problem. I moved one of my workstations into my new AD domain and found that no matter who logs into the machine, even a Domain Admin, they can not access the Exchange 5.5 server. I've tried deleting all of the profiles from the machine, I've tried pulling the machine out of the AD domain and adding it back in. I've checked to make sure that the Outlook security is set to no password. No matter what I've tried, I get the "You do not have permission to access...." when trying to setup a Exchange 5.5/Outlook profle on the computer. I can browse the server where Exchange resides. It also serves as a File Server and I can access all the shares on it. I did not migrate the NT Domain into an AD domain, I created a parallel domain and setup a two way trust between the NT PDC and Active Directory 2003 server. The trust seems to work in any way I can test it and I've moved other machines in this way without problem. Since it happens to anyone who logs into that machine, I can only assume the problem is with the PC itself, and not with the user accounts. But what could that problem be?
0
mikejcurtis
Asked:
mikejcurtis
1 Solution
 
gnegrotaCommented:
Antivirus software ? The Workstation are running (???) OS ?
Other Network-related software installed on workstation ?
0
 
mikejcurtisAuthor Commented:
Silly me. SAV Corporate edition v10.1, Workstations are XP SP 2, M$ Office 2003 suite, and other non-network Specific software packages.
0
 
mikejcurtisAuthor Commented:
I should add that when I setup the email account from the machine and do a Check Name, the name underlines. But once we've completed that There's no more goin' there.

I also don't wish to sound like a smart-alec with the 'silly me' above. It's just that I'm on hour 10 after only 4 hours of sleep if you know what I mean?
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
paulhekjeCommented:
Is the XP firewall enabled?
Access to a trusted domain can be problematic even with the "firewall's domain profile"
0
 
gnegrotaCommented:
Drop Xp from domain ( switch to workgroup ... ) [reboot] , reset Local Policy ( gpedit.msc , and load Workstation template ) [reboot]  , reinsert XP in Domain ( be sure to have WINS server added in TCP/IP Advanced ... Not for XP but for Exchamge 5.5 ...) [reboot] .
Tell me the status after ...  

( yeap , I know how it is ... about your 4 hours. It's ok ! ;) )
0
 
gnegrotaCommented:
A, btw ... keep Sophos down ;) . Activate it after !
0
 
mikejcurtisAuthor Commented:
gnegrota, I'm in gpedit.msc, but I don't see where I can reset Local Policy and I'm not seeing the WorkStation template, I do see other Administrator Templates
0
 
mikejcurtisAuthor Commented:
Also, I looked at each setting in what I find there and it all says "Not Configured".
0
 
gnegrotaCommented:
Mea culpa ...

Secpol.msc and import compatws.inf

0
 
mikejcurtisAuthor Commented:
Paulhekje, I disabled the firewall, same result; "You do not have the right to login..." Phoo.
0
 
mikejcurtisAuthor Commented:
I finally found the solution! The Office install was corrupted. I uninstalled Office and reinstalled it and everything worked. My user was able to access email without issue. Thank goodness!
0
 
mikejcurtisAuthor Commented:
How do I get this Question closed? I solved it myself.
0
 
NetminderCommented:
Closed, 500 points refunded.
Netminder
Site Admin
0
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