PDA

Click to See Complete Forum and Search --> : WINS takes a full minute to resolve

Fubarian
March 30th, 2004, 11:55 AM
When you're a user, it takes a minute -- when you're admin, its instant. Registry permissions seem to line up but its for anyone thats NOT and admin -- any ideas?
Matridom
March 30th, 2004, 12:43 PM
When you're a user, it takes a minute -- when you're admin, its instant. Registry permissions seem to line up but its for anyone thats NOT and admin -- any ideas?


have you checked nbtstat to see how it's comming up with the resolution?
Fubarian
March 30th, 2004, 12:49 PM
have you checked nbtstat to see how it's comming up with the resolution?hmm, says failed to access netbt driver

looking for a place to turn it back 'on' ...

found it, helper service was trying to use a stupid account. still taking a minute to resolve.
Matridom
March 30th, 2004, 03:05 PM
hmm, says failed to access netbt driver

looking for a place to turn it back 'on' ...

found it, helper service was trying to use a stupid account. still taking a minute to resolve.


So i'm assuming it's saying that it's getting to the wins server this time?

If so, is it retrying often? defaulting to broadcasts?
Fubarian
March 31st, 2004, 07:53 AM
So i'm assuming it's saying that it's getting to the wins server this time?

If so, is it retrying often? defaulting to broadcasts?no it isn't. even pinging the wins itself comes up with the 1 minute delay.

Microsoft sent me this article from one of the public boards but its for 2k and not 03 (I know they're very similar) but I'm wondering what in the hell is goin on. After we ran a restore on one of the terminal server boxes, its now resolving correctly -- yet they have the same services running, same OS, same install, same patches ran....everything.

Here's the MS article
329405 - DNS Name Resolution Does Not Work for Users Who Are Not Administrators (http://support.microsoft.com/?id=329405)
But again, nothing for 03