Windows Server

skitrees · Guest

I have been using Windows 2003 Small Business Server for over a year now.
I've had a persistent issue which has survived even after reformatting and
reloading the Windows 2003 Small Business Server machine.

Here it is:
The client machines can logon to the domain. Things work great for a few
hours. No problems - all access is fine, and the system in entirety is
running perfectly with no abnormalities. After a few hours, however, the
clients seem to lockup for several minutes if the user attempts to access a
shared folder on the server. The server will eventually send a request back
to the client for username and password. If I enter the user I am currently
logged on under - it will give me an error stating that this user is already
logged on and has already tried to authenticate, and it won't let me on. I
have to logon to the share as an administrator in order to gain access. The
only other option is to simply restart the local clients - this fixes the
problem for a couple hours again.

I have run gpupdate on the clients, I have created a batch file to run
ipconfig /release, ipconfig /flushdns, and ipconfig /renew on the clients -
this actually will occassionally resolve the issue, but only like, 2% of the
time.

Any help would be greatly appreciated. If I have been unclear, need to post
this somewhere else, or if you need further information from me - please let
me know and I will do my best to follow whatever instructions are set out.

I have setup several Small Business Server Machines without any problems.
However - go figure - this one in my office has presented me with this odd
issue that I can't seem to track down.

Thanks!!
Skitrees

John Smith · Guest

have you tried a fresh install of the client OS (winxp?)?
and put the client pc/user in an OU that has no gp's.
event logs? anything there?
try running network monitor on the server too.

On Sun, 16 Jan 2005 19:37:03 -0800, skitrees wrote:

skitrees · Guest

John,

Thanks for your reply. Yes, I have tried a fresh install of the client OS
on ONE of the clients (all clients on the network have the same issue). All
are running WinXP Pro. I've tried the OU approach with no GPs as well.
Event logs always show everything is running good. No failures anywhere -
except the logging of the same error I see on the screen about "user cannot
logon twice" or whatever it is (though I'm not trying to log on twice - I'm
simply trying to access my share).

If I can provide any further information that would help out - please let me
know.

Thanks again for the quick reply.

"John Smith" wrote:

skitrees · Guest

John,

Thanks again for responding so quickly!

You pointed out the blindness I had obtained from working too close on this
- I had forgotten to check the client Event Viewer(s). It appears that I
begin receiving "autoenrollment" errors:

"Automatic certificate enrollment for local system failed to contact the
active directory (0x8007054b). The specified domain either does not exist or
could not be contacted.
Enrollment will not be performed.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp." Event ID 15.

I'll go out and see what I can find pertaining to this in the knowledgebase.

Arghhhh!!! Do I feel stupid now!

Thanks for pointing me in the right direction!!

Skitrees

"John Smith" wrote:

John Smith · Guest

have you looked in the event viewer on both client & server when this
happens?

what is the exact error that you get?

i assume all machines/users are members of the domain?

install network monitor (add/remove windows components) on the server (or
ethereal on xp) and see what's going on behind the scenes.

On Sun, 16 Jan 2005 21:39:08 -0800, skitrees wrote:

skitrees · Guest

John,

RESOLVED!

Thanks for the help - found the improper entry was due to a router handing
out itself as the primary DNS server!

Thanks for replying - you pointed me in the right direction!!

Thanks

"John Smith" wrote:

	Windows Server Forum Index -> DNS	All times are GMT
Page 1 of 1