Issue with shares in Server 2003

[Katana]

I've got a problem with shareing a folder in server 2003 enterprise. I have a folder shared on a file server so that everyone can access it but only the domain server is able to access over the network. I get an error that says "There are currently no logon servers available to service the logon request" when trying to access from client PCs. The client PCs can access the domain server just fine, it's just the file server that I am haveing issues with. Both the domain and file servers are running Windows Server 2003 Enterprise with the domain server set up as the DHCP, DNS, and WINS server as well. Any help greatly appreciated.

 

[Katana]

A little more info.

All client PCs are running XP Pro. I've tried rejoing a client to the domain with the same error after rejoining. The share was working last week, I don't believe I have changed any settings, but this week it is not working. The file server has a static IP that I setup on the DHCP server with all the client PCs haveing dynamic IPs assigned by the DHCP.

 

[seepy83]

Any reason you are running WINS?

With all Server 2003 and XP Pro machines, I don't think you'll need it. Try disabling WINS and use only DNS.

 

[Katana]

Right now we are only running XP but we have some equipment that uses 98 coming in. I'll still try disabling WINS tonight to see if that helps.

 

[RebateMonger]

Well, WINS likely isn't causing the problem. If DNS is available, the clients will never even look at the WINS data.

Are you sure that DNS is set properly on the file server? If the Domain Controller is the only DNS server, then the file server should ONLY list the DC in its list of DNS servers. Try running NSLookup on the file server, as well as DCDiag.

 

[spidey07]

That really sounds like a DNS problem. The client is telling you the problem - it can't locate a logon server for the request. That is done via DNS.

-edit-
And WINS. So I'm inclined to believe it is a name resolution problem of some kind.

 

[TheKub]

I concur with the name resolution suggestions. NSLookup should help. Also have you thumbed through the various event logs?

-Edit

Also when you say the clients can access the domain server fine what do you mean? Logging in\file share\etc? Just because your clients are logging into the workstation doesn?t exactly mean you connected to the domain. In most cases if they cant hit a domain controller they can still sign on using cached credentials.

 

[Katana]

I tried nslookup, here is what I get back

DNS request timeout
Can't find server name for address 109.168.0.2 (DC)
Default Server: Unknown
Address: 192.168.0.2

I thought I had all the DNS settings correct but apparently not. Here are my DNS settings;

Under Server Properties
Interfaces - I have only the following IP addresses checked with 192.168.0.2 as the IP address
Forwarders - ISP DNS
Advanced - Bind secondaries, Enable netmask ordering, and secure cache against pollution checked
name checking: multibyte
load zone data on startup: From Active Directory and Registry

Forward Lookup Zones - _msdcs.atrona.local and atrona.local

Reverse Lookup Zones - 192.168.0.x subnet




When I said the client can access the domain I mean when I type \\server I can access shared folders on that server. For the file server I get the error.

 

[imagoon]

All machines, including the domain server and file server need to have DNS set to and only to a DNS server that is in the domain. There *MUST* not be any other DNS servers in the DNS list on any of thoses machines while they are in your network. As for WINS, it is best to install the WINS server on the 2003 server and let it handle being the domain master. Authentication is a 2 way street. The client is going to try and connect to the file server and the file server is going to try and authenticate to the D/C for the incoming connection. Both machines need to be able to talk to the domain controller. DNS and WINS configurations can be handed out by DHCP.

All outside DNS should be handled by the DNS server on the domain controller. That error is a DNS error that typically happens when someone thinks it is "best" to have outside internet DNS in the DNS list of the clients.

Verify you have a machine account on the file server and that the file server has successfully joined the domain.

Do an ipconfig /all on the DC, file server, and a random client that is having issues.

Ignoring the fact that I don't have a domain at home...

IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 4.2.2.1
4.2.2.2
4.2.2.3

DHCP, default gateway, subnet, and DNS (in most cases) should be identical on all machines. I am assuming you are not doing multi-site networks with WAN connections however...

Another thing to look for, make sure you do not have a DNS zone of "." While not likely to be the cause of the issue it might be a symptom of someone entering internet DNS servers in workstations to try and get to the web. "." makes Windows DNS become a root server, 99.99999% of the time, you don't want that.

 

[RebateMonger]

Originally posted by: Katana
DNS request timeout
Can't find server name for address 109.168.0.2 (DC)
Default Server: Unknown
Address: 192.168.0.2

The "Can't find server name for address..." error usually happens because there's no reverse DNS lookup for that DNS. It can happen if Reverse DNS isn't set up or is incorrect. It's usually not a problem by itself.

 

[Katana]

So I feel like a bit of an idiot. Last week I had some issues with Vista (that's why I'm on XP only now) and had to reinstall the DC but forgot to rejoin the file server to it. Everything is humming along nicely now, thanks for all the suggestions and help.

 

[deaner]

Originally posted by: Katana
So I feel like a bit of an idiot. Last week I had some issues with Vista (that's why I'm on XP only now) and had to reinstall the DC but forgot to rejoin the file server to it. Everything is humming along nicely now, thanks for all the suggestions and help.

OH....yeah, that I'll do it to you.