|
Why would this only affect XP clients?
I do not have the same problem when using Win2K Pro clients from the outside
network. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas M. Long The problem is you are using two totally
separate DNS’ , not to mention you probably have a firewall between you
and the Exchange server when on the public network…unless I got totally
lost reading thisJ From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edwin I created this thread a while ago but
something came up that took priority over this question. I would
appreciate it if I could continue to get help on this topic. “For the first user, I assume then that you realize the answer
right?” No, I do not know the answer to this. Could you share this
information with me? I do have Audit Logging enabled, but assuming that I am not overlooking
anything, I do not see anything of relevance in the messages. Is there
something in specific that I should be looking for? From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mulnick, Al For the first user, I assume then that you
realize the answer right? For the other users, see below for
questions relating to the scope and steps so far taken. Add software in
use to find out what's different about those 2K workstations that have a
problem. Al From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edwin I was informed of this problem today and
it is with a certain individual who uses their laptop on the public
network. When he uses that same laptop from within the network all is
buttery! In a totally separate event that I was
looking into, I noticed that some people were getting the same error.
These workstations have Win2K Pro installed and are on a Win2K3 domain.
If the user within the domain hit the "RETRY" button, it works. I myself am operating under the same GPO's
and other related settings as the person who is getting the RETRY prompt from
within the network but I do not get that error from my workstation. From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Mulnick, Al That depends. What's the entire scope of the
problem? One machine? Three machines? All machines? That
makes a big difference for the solution that needs to be used. What gets logged on the domain controller
when you attempt this (assuming you have audit logging enabled)? What happens on the wire during the
attempts? Network trace? From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edwin Recently I was informed that users attempting to connect to
our Exchange server when using WinXP are experiencing troubles. The error
is that it cannot connect to the exchange server. I do not see any errors on the client XP machine or on the
Exchange server itself. For some reason I am able to open the MAIL application
within the control panel and successfully connect and authenticate to the
Exchange server. But when you do a "Check Name" the error is
returned that it could not connect. I found an article on Microsoft's site but it seems a bit
extreme. http://support.microsoft.com/default.aspx?scid=kb;EN-US;255843 Has anyone else encountered this? Was there an
alternate solution? Thank you all for your replies. Edwin |
- RE: [ActiveDir] Exchange Authentication and WinX... Edwin
- RE: [ActiveDir] Exchange Authentication and... Mulnick, Al
- RE: [ActiveDir] Exchange Authentication and... Douglas M. Long
- RE: [ActiveDir] Exchange Authentication and... Cothern Jeff D. Team EITC
- RE: [ActiveDir] Exchange Authentication and... Joe Pochedley
