Re: Cross Domain Connection Issues

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Blaze (asda_at_ssfsdf.com)
Date: 02/21/05


Date: Mon, 21 Feb 2005 23:19:05 GMT

Thanks for the info Steven... but I can from each domain find the other
servers and clients on the other domain by pinging the client/server names
and I get an ip resolution..?

would this be the issue you are trying to resolve ?

Thanks

"Steven L Umbach" <n9rou@nospam-comcast.net> wrote in message
news:OzJMUC6FFHA.3596@TK2MSFTNGP12.phx.gbl...
> You could try to recreate that trust or use nltest to reset it.
>
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;158148
>
> More than likely you have a name resolution problem to fix first - either
> netbios or dns. Try to ping each domain controller in domain A from domain
> B by IP address and name, both netbios and fully qualified domain name to
> see what happens. If using wins, have the wins servers in each domain
> replicate with the wins server in the other domain. Make sure the Windows
> 2000 domain controller is configured to have a secondary dns zone for the
> Windows 2003 domain and that it is replicating properly. The Windows 2003
> domain can simply use conditional forwarding to the Windows 2000 domain
> controller for dns name resolution of that domain. If you are not using
> wins you can try using a lmhosts file on the pdc fsmo in each domain to
> point to the pdc fsmo in the other domain. --- Steve
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;314108 --- how to
> create lmhosts file. Note that syntax is case sensitive and that the saved
> lmhosts file must not have an extension.
>
> "Blaze" <asda@ssfsdf.com> wrote in message
> news:618Sd.398$u56.240@newsfe5-win.ntli.net...
>>I have 2 domains, Domain A has 2 W2003 DC's and Domain B has 1 W2K DC.
>>
>> The 2003 servers have just been upgraded and there was a 2 way trust
>> between the Domains..
>>
>> This 2 way trust was reset up with the New Domain A 2003 server
>>
>> When I log onto Domain B client as a Domain B user and I try to acess a
>> folder on Domain A I get a "there are currently no logon servers
>> available to service the logon request" Error
>>
>> When I log on to Domain B as a Domain A user everything works fine.
>>
>> When I go onto Domain B's Trust MMC and click verify for Domain A i get
>> the following error.."the secure channel (sc) reset on the domain
>> controller to failed with the error there are currently no logon servers
>> available to service the logon request"
>>
>> Help... Any Ideas
>>
>> Thanks
>>
>
>



Relevant Pages

  • Re: Help attempting to get hacked?
    ... I am experiancing similar issues with Win98 Clients ... >indicate that you are also using a W2K rras vpn? ... If your rras servers are all W2K, ... >domain controller. ...
    (microsoft.public.win2000.security)
  • Re: Cross Domain Connection Issues
    ... servers and clients on the other domain by pinging the client/server names ... Try to ping each domain controller in domain A from domain ... have the wins servers in each domain ... > wins you can try using a lmhosts file on the pdc fsmo in each domain to ...
    (microsoft.public.win2000.setup)
  • Re: Cross Domain Connection Issues
    ... servers and clients on the other domain by pinging the client/server names ... Try to ping each domain controller in domain A from domain ... have the wins servers in each domain ... > wins you can try using a lmhosts file on the pdc fsmo in each domain to ...
    (microsoft.public.windows.server.networking)
  • Re: Cross Domain Connection Issues
    ... servers and clients on the other domain by pinging the client/server names ... Try to ping each domain controller in domain A from domain ... have the wins servers in each domain ... > wins you can try using a lmhosts file on the pdc fsmo in each domain to ...
    (microsoft.public.cert.exam.mcse)
  • Re: Trust relationship W2k - NT4
    ... the lmhosts file at the nt4 side works ¡¡¡¡¡¡¡¡¡¡¡¡¡ ... > then see if you can add users from the NT4 domain ... >> domain controller for the domain was not found. ...
    (microsoft.public.win2000.networking)