There are currently no logon servers available to service the logon request - how to fix this error?

There are currently no logon servers available to service the logon
request - how to fix this error? i get it when trying to access a share one
hop away.
here is port scan from the machine i am using to try to access the share of
the machine with the share:
Interesting ports on <domain name>:
Not shown: 1696 closed ports
PORT STATE SERVICE
80/tcp open http
135/tcp open msrpc
139/tcp open netbios-ssn
445/tcp open microsoft-ds
1031/tcp open iad2
2301/tcp open compaqdiag
3389/tcp open ms-term-serv
9535/tcp open man
MAC Address: <mac addy> (Compaq Computer)
Device type: general purpose
Running: Microsoft Windows 2003/.NET|NT/2K/XP
OS details: Microsoft Windows 2003 Server Standart Edition SP1, Microsoft
Window
s 2003 Server, 2003 Server SP1 or XP Pro SP2
Network Distance: 1 hop

If this is within a domain environment are you sure you are
using a machine configured to use only the correct DNS servers
that are able to support the domain?

is DNS configured correctly on the host and the server? Can you do an
NSLOOKUP against the domain for a DC?

Assuming it is SBS Standard,
Your server should only have one network card and one IP address
The DNS Server address should be itself only. No other addresses and
especially no external addresses.
The DNS Service should be set up to use either Root Hints, or an external
DSN Server as a forwarder (your ISP's DNS Server)
Start from there and let us know how you get on,

Ok...to put it more simply
You have a server...apparently running some version of Windows Server
2003....(is it small business server 2003?)
You have a workstation that can't access a share on that server

Am I right so far?

If so, please post the results of running IPCONFIG /all on the server...and
the problem workstation
Post exact output...please don't mask it or it makes it real hard to
troubleshoot

Could you provide the following information:
1. Domain or workgroup environment?
2. What is the edition of client and shared computer.

If you are in the domain enviroment, please ensure that the computer is
able to connect to DC. Follow these steps:
1. Ping DC Name and IP Address from the client and shared computer.
2. Access shared folder on DC.

I suggest you try to access the shared folder from other computer, to see
if the problem occurs.

Please update me with the above results, so we can perform further
troubleshooting.

[eletromania]

A simple restart of the machine should fix the problem.

Sometimes the 2 computer connecting to each other lose connection and cant authenticate. You can still ping the destination but cant browse for example a shared folder which only a particular security group can access. It's due to lost connection and authentication.

Hope this helps...

[ssalb]

I have this same problem. Restarting my workstation solves the problem -- but it gets old, fast! If I try to do a netdiag or anything else (like nltest, I get "can't find ____: Non-existent domain." If I try to ping, same problem.

How can I diagnose this problem?

Yes, your server should be there.
Can you describe how your server and DNS are set up?

ipconfig on my server reports that my server's ip address is 192.168.1.137.

BUT I am getting an error report in my Event viewer that says, "The DNS server encountered a packet addressed to itself on IP address 192.168.1.137. The packet is for the DNS name "x3.x00space.com.". The packet will be discarded. This condition usually indicates a configuration error. Then it suggests checking forwarders list, master lists of secondary zones, notify lists of primary zones, delegations of subzones, and root hints.

Within DNS, my Forward Lookup Zones does include my server (with the .137 ip address); is that supposed to be there?

I'm not really sure where else to look. Any help?

I think you've asked me a question I don't know how to answer!

I know that I have Windows SBS 2003 installed on a Dell server. I know that the Windows DNS server is running on that machine.

I know that I have lots of warnings and Errors on my DNS Event Log, including:

---
DNS server has updated its own host (A) records. In order to ensure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update. An error was encountered during this update, the record data is the error code.

If this DNS server does not have any DS-integrated peers, then this error
should be ignored.
---

OK, so I should be able to ignore that one, right?

But I also have a series of Warnings:

---
The DNS server encountered a packet addressed to itself on IP address 5.178.218.163. The packet is for the DNS name "www.emsg.net.". The packet will be discarded. This condition usually indicates a configuration error.

Etc.
---

(And the same thing referencing 192.168.1.137.)

This seems potentially more meaningful.

I've got Forward Lookup Zones of _msdcs.lssoffice.local and lssoffice.local.
I've got Reverse Lookup Zones of 192.168.1.x Subnet

(Is this the information you asked for?) I can tell you more from the server DNS properties. My name server has an FQDN of server2.lssoffice.local (the IP Address is stated as Unknown).

When I run a test using the Monitoring feature, they pass.

[lk247]

It appears that (in my case) it is a problem with the domain controller of the system you want to connect with.
I had a similar problem with a virtual server, running on the laptop. No problems to connect from the vm-server to the host, when situated in the office. Working at home: "There are currently no logon servers available to service the logon request".

After digging through the internet, netbeui settings, tcp/ip stack rebuild, it didn't work!

Finally, I set up an vpn connection to the office network from the host laptop and all of a sudden I could connect from the vm-ware server to the host laptop!

I hope this is of use for others facing this problem.

I have computer at a remote site connecting with VPN connection to our local office. Can I connect via the internet from the remote pc to my local pc? If yes what to I need to do to make this work?

[ganesh5642]

Error:
\\10.40.9.101 is not accesible. you might not have permission to use this network resource. contact the administrator of this server to find out if you have access permissions.
There are currently no logon servers available to service the logon request.

here iam accessing the sharing data in the server 2003. and iam accessing through windows professional(service Pack2).
server IP is 10.40.9.101 and DNS is also same.
workgroup system ip is 10.40.9.100 and Preffered DNS is 10.40.9.101.
Here iam accessing data through Run prompt. It will show the above error.
Plz Help me to solve this problem.

[pc_tim]

I had the same issue, where when I tried to connect one computer to another is would give me the same error message. I searched high and low for the answer, with no success.

Then it came to me, check to see if Simple File Sharing was turned on. It was, as soon as I shut that off, the computer connecting to the "server" computer would finally prompt me for a user name and password.

To shut that off:

On the "server" computer go to Control Panel, on the file menu choose Tools | Folder Options. On the View tab of that window, scroll down to the bottom and uncheck "Use Simple File Sharing".

I believe another way around this, would be to have the same account on both computers with the same password since it is "Simple" file sharing. I haven't tested that, but in theory that should work. I hope this helps.