\\fileserver is not accessible. You might not have permission to use this network resource. Logon failure: the target account name is incorrect.


hi,

i face problem new added server or workstation cannot access old w2008 sp2 file server host name or fqdn. can access file server by ip. other old servers can access file server without problems. error:

\\fileserver not accessible. might not have permission use network resource. logon failure: target account name incorrect.

what have tried:

1. disjoin file server domain, delete ad account , join again win different name , ip.
2. delete dns , wins entries , reregister dns , wins entries.
3. ip, dns , wins entries same server.
4. firewalls off.

but not help. related authorization. is else can do?

thanks

hi,

dns pointing should configured proper on new added servers, domain controllers , domain members.

configure dns settings on dc , members per below article.
best practices dns client settings on dc , domain members.
http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/

once done above, run below commands:
net stop dns & net stop netlogon & ipconfig /flushdns & net start dns & net start netlogon & ipconfig /registerdns

also clear cached credentials on problem machine using net use /d *

still issue persist see artricle:
resolving network issues-you might not have permission use network resource
http://blogs.technet.com/b/danstolts/archive/2011/06/21/resolving-network-issues-you-might-not-have-permission-to-use-this-network-resource.aspx

if still issue reoccurs post dcdiag /q , ipconfig /all from dc , problem machine.


best regards,

abhijit waikar.
mcsa 2003 | mcsa:messaging | mcts | mcitp:server administrator | microsoft community contributor | my blog

disclaimer: posting provided "as is" no warranties or guarantees , , confers no rights.



Windows Server  >  Directory Services



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607