[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1053
  • Last Modified:

There are currently no logon servers available to service the logon request

Hello

I am having trouble accessing shared resources across a remote network. The setup is as follows:

ClientA - DOMAINA - Windows XP SP3
ServerA - DOMAINA - Windows 2003 Standard - PDC
ServerB - DOMAINB - Windows 2003 Standard - PDC
ServerC - DOMAINB - Windows 2003 Standard - Member Server

DOMAINA and DOMAINB are trusted domains, both way.

ServerA and ServerB are recognised in the others WINS configuration.

ServerA can access a shared drive on ServerC
ClientA can ping the IP address of ServerC but cannot ping it by name.
ClientA cannot access a shared drive on ServerC via name or IP address.

The problem is that we want ClientA to be able to map network drives from ServerC. I cannot for the life of me figure out why ServerA can access the shared resources on ServerC but ClientA, that's on the same domain as ServerA, cannot.

Any help appreciated!


0
puterssupport
Asked:
puterssupport
  • 6
  • 6
  • 2
2 Solutions
 
Kieran_BurnsCommented:
Have you got forward lookup up zones for each domain created in DNS? If not this is why pinging by name is not working
to create the lookup zone you need to ensure that the Servers can transfer zones to each other.
On each Domain, load up the DNS console, right click on the domain name, choose the Zone Transfers tab and add the Server IP addresses of the other domains DNS Servers. (or pick To any Server) tick the 'allow zone transfers' box and click OK
Now create the forward lookup zones as a secondary on each DNS Server and check that zone transfers work (right click the newly created zone and choose 'transfer from master'
You should now find pinging by name working as well as being able to access shared resources
0
 
puterssupportAuthor Commented:
Hello Keiran,

Thank you for your suggestion. I can confirm that the forward lookup zones for each domain have been created and that zone transfers work okay.

However, the problem still persists on ClientA.

0
 
Kieran_BurnsCommented:
have clienta run ipconfig /registerdns
you could also try using the FQDN for the server name to see if it is at least picking up the DNS entry correctly
So rather than \\servername try \\servername.domain.com and see what happens
Also ensure that clienta is seeing its own DNS Server correctly (I know, but it's always best to check :-) ) Try running an NSLOOKUP on clienta for its own domain resources and try again for the remote domain resources and see what happens
0
A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

 
puterssupportAuthor Commented:
Hello

I have tried your suggestions, which were inconclusive.

I cannot browse to the share via IP address either - eg; //192.168.100.3/
0
 
Kieran_BurnsCommented:
Just to check - you are using \\ rather than // aren't you?
0
 
puterssupportAuthor Commented:
Haha - Yes ofcourse, just a typo on my part! Only seen to get them right if it's a run or cmd box.

The local DNS settings on both domains are fine as far as I am aware. The PDC's are also the DNS Servers.
0
 
Kieran_BurnsCommented:
So - your DNS is working, and you have forward lookup zones for each domain being updated within the DNS structure on all Servers?
From the client p.c. you can ping resources on the local domain by name but not resources on the remote domain?
What happened when you tried NSLookup? Did you try changing the Server to the remote domain server (by ip address) within NSLookup?
I hate to suggest it, but have you added a WINS entry in on the client p.c.?
0
 
puterssupportAuthor Commented:
Yes - that's correct. the secondary lookup zones are updating okay, on both servers.

That's almost the case.
From ClientA I can ping ServerA using name and IP.
From ClientA I can ping ServerB using name and IP.
From ClientA I cannot ping ServerC using the Netbios name. But I can ping using FQDN and IP.
From ClientA if I try and access the shares on ServerC using the IP or FQDN I get the error message: There are currently no logon servers available to service the logon request

Using NSLOOKUP on ClientA - I can only resolve ServerC using the FQDN.

I do not think this is a DNS issue as I cannot access the share via IP either.

Thank you for your continued assistance!
0
 
Kieran_BurnsCommented:
He he - it's an AD issue, so it must be DNS ;-)
Okay - let's introduce clientb.
Can a client machine on  the same domain as ServerC access the shares and the Server by name?
 
Oh and ServerC doesn't have multiple active network cards does it?
0
 
puterssupportAuthor Commented:
Hello

Yes - clients on DOMAINB can access shares on ServerC by name.

Nope - just one NIC.
0
 
Kieran_BurnsCommented:
Try adding a DomainB DNS Server as the PRIMARY DNS for ClientA, and that really will prove it is DNS or not. Reboot the p.c. after making the change
Could you also add a print out of the Ipconfig/all settings for ClientA and a Client on the DomainB network as well?
0
 
puterssupportAuthor Commented:
I can view shares on ServerB on ClientA but not ServerC.

There's definitely nothing wrong with the settings on ClientA.
0
 
ChiefITCommented:
It sounds like you have both DNS and netbios problems:

Netbios is used by the master browser service to populate and assist in sharing file shares. It is also used for netbios translation to IP address for ping and the My Network places.

However, netbios is not a routeable protocol. this means it will not go over nat, through a VPN tunnel or across a firewall.

for your original question, google search "Chiefit there are currently no logon servers"

I am sorry I couldn't search for it myself. Looks like my satellite connection is going out.
0
 
ChiefITCommented:
OK, signal better:

We must have pulled out from behind a hill.

I have helped many people with the browser service and DNS. It sounds like you have both:

Your original error: "There are currently no logon services available to service your request:
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_23356031.html

Then, your file sharing issue has to do with netbios not being routeable.
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Q_23652843.html


0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 6
  • 6
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now