DNS Problem?

[homer15]

hey everyone,

something strange has been happening around here. when some of our machines try to access a share on 1 specific server, it gets an error saying:

\\server is not accessible. you might not have permission to use this network resource. contact the administrator of this server to find out if you have access permissions. logon failure: the target account name is incorrect

when i access these same shares by going directly to the ip, everything comes up just fine. i think it's the dns servers, but i've reset the services on both and it hasn't made much change.
neither the client or the server or the dns servers have anything in their logs.
the probelm is sporratic. on some machines, they won't be able to access the programs but after a restart it will work fine. on others it just won't work at all. and some of our machines have no problem.
any ideas on what i could try next?

[homer15]

all of the workstations are windows xp, the server they're trying to access is windows 2003 and the two dns servers are windows 20000 server

[homer15]

^bump^

[Detonate]

I don't have an answer for the DNS problem, but unless you are talking about a large number of workstations, you could simply modify the hosts file on each of those work stations, since you are able to connect by IP this should work.

[homer15]

thanks. that would be a workaround for the problem, but not a fix. i'm a big fan of applying bandaids first to get people working, and then fixing the core problem.

the workaround i've currently done is to set this particular server as the primary dns server for all workstations, and then set my pdc as the secondary

[Force Flow]

Check the WINS server.

[homer15]

i think i fixed it. one of my domain controller's dns client seized up. it didn't spit out any errors or any log entries, but it was not repsonding. as a result, my pdc wasn't replicating properly and it was causing some permissions issue.

now that that's solved, i'm wondering why my pdc wasn't letting me know it was not resolving the other controller and not replicating. i looked around, and it should've made some kind of log entry. i guess i'll see what's up with my logging.

[Force Flow]

I can't say that the domain controllers I work with spit out something in the log when one of them goes down (I've had reboots for windows updates and freezes due to power issues).

[homer15]

it makes the job interesting, right? haha.

[Force Flow]

new day, new problems