Re: Unable to authenticate to untrusted domain NTLM v2 related issue

After reading your original post more carefully it seems that there is no
trust between the domains. If your domain is not a trusted domain then you
can not use accounts in your domain to access recourses in the other domain.
You could either use local accounts on or use a user account in the other
domain from your computer.

Steve


"lwoody7110" <lwoody@xxxxxxxxxxxxx> wrote in message
news:1158150807.703689.6050@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks Steve. I will look at this after Roger has had a chance to
advise me on the questions I have answered for him.



.

Relevant Pages

  • Re: Single Sign On?
    ... on multiple ports. ... The customer access is via the internet and they ... domain becuase there is no level of trust with their network. ... The customer users our domain accounts to ...
    (microsoft.public.win2000.active_directory)
  • RE: question about creating an external domain trust Server 2003
    ... You would Create accounts in the Trusted ... domain and put them into groups to access foreign resources. ... NETDOM to create the trust. ... F1child to be used on the webserver. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Single Sign On?
    ... The customer access is via the internet and they ... authenticate using basic authentication and SSL via ISA. ... domain becuase there is no level of trust with their network. ... The customer users our domain accounts to ...
    (microsoft.public.win2000.active_directory)
  • Re: This is about computing
    ... If you cannot trust her enough to share ... Give my wife access to my online banking password. ... courts here to grant her full access to my accounts which she may need ... access then the courts will not be a problem. ...
    (comp.programming)
  • Re: Deploying Sharepoint across two domains
    ... I am looking into having a trust between the two domains. ... > The service accounts and the user accounts that portal uses from a directory ... > sorts off errors because as far as the SharePoint application is concerned ... >> not exist despite being the same account I am using to create the config ...
    (microsoft.public.sharepoint.portalserver.development)