Windows Forum

Ask something
Discussion Locked

WINS? Error

0 helpful
11 replies

by jw01234

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

There is a server on the DMZ that I'm trying to connect to. I can ping it. I can tracert it. I can connect to it using Hyena. I can connect to other servers on the DMZ using \\ipaddress\c$. But I can't use the command line "\\ipaddress\c$" to connect to it. When I try this, I get the message: "There are currently no logon servers available to service the logon request." On TechNet, article Q139410, describes this as a WINS error. I don't think it is because the server is on the DMZ, which (obviously) doesn't use WINS. A colleague mentioned that this might be a configuration error, but I can't find where. The external dns entry is different from the machine name and therefore the host name under the dns entry in network properties.

Any hints? The user who wants to connect to this machine is breathing down my neck.

11 replies

by mphoffar

I think you're right in this isn't a wins issue. If I'm reading you correctly, the DMZ is separate from the rest of your domain. This sounds more like something wierd with the trust between the DMZ and the domain you're on not preventing you passage into it.

Just a thought...

Mark

by jw01234

Acceptable answer. There is no trust, all the machines on the dmz are stand-alone servers. When I connect to a machine on the DMZ, it prompts me for a username/password. Instead, I get the no logon server available message.

by allan

Does Hyena show the C$ share, if not you may need to reboot the machine.
Try sharing another folder and connecting to that share.

by jw01234

No, hyena doesn't show the admin shares. I tried connecting to the server via another share, but again, got the same error.

by tigre_269

Jeff,

Are the admin shares being created? Is the Server service running? I agree with you, it's not a WINS issue. I had the same problem. The admin shares were not being created upon boot up. One of the admins disabled it in the registry, through poledit. The setting is located in; File, Open Registry, Local Computer, Windows NT Network, Sharing, create hidden drive shares(server), check the box.

by allan

If Hyena doesn't see the shares then you have to follow the previous post and get them going.
Because you can't seem to connect at all I'd double check that the workstation and server services are running.

by mpdcsup

Is the Net Logon service running on the target machine? Is the machine configured with the name of a Domain? Or, does the Identification tab of the Network applet say, "Workgroup"? Does the workgroup specified have the same name as a know NT domain inside your organization?

What is happening is that when you specify \\srv1.your.com\c$, NetBIOS locates the resource (usually with the help of WINS) and submits your credentials (username, password, NT domain) to the resource host for validation. In an NT domain environment, unless you and the resource are in the same domain, the authentication request is forwarded to the PDC for verification (thus the blatancy of the message you're getting and the Knowledgebase Article).

If your machine is *truly* stand-alone (i.e., as implemented vs. as intended) then the authentication is handled by the Net Logon Service on the resource host.

It wouldn't hurt to ensure the following services are running:
- Computer Browser
- Messenger
- MSDTC
- NT LM Security Support Provider
- Remote Procedure Call (RPC) Locator
- Remote Procedure Call (RPC) Service
- TCP/IP NetBIOS Helper

If all else fails, check the Access This Computer Remotely User Right in User Manager forDomains.

This discussion is closed to new replies.