Windows 7 Professional Client cannot access shared folder on Windows 2008 Server

We changed the computer name on a Windows 7 Professional client and now it cannot access a shared folder on a Windows 2008 server in a Windows SBS2003 domain environment. The SBS2003 is the domain controller and the 2008 server is an application server. The client can access shared folders on the SBS2003 server but not on the 2008 server. The error message received is;

 \\SHAREDFOLDERNAME 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.

I have already tried removing the client from the domain and adding it back and that did not resolve the problem. Also, when viewing the network from the client, the 2008 server is visible but not accessible. Likewise, when viewing the network from the 2008 server, the client is visible but not accessible.

Tech support for the application said the 2008 server is remembering the host name associated with the original MAC and we need to find a way to reset the hostname/MAC on the 2008 server but I don't know how to do that.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

How did you change the name, using netdom?
Check whether there are stale sessions on the 2008 server. Computer management, shares, share sessions.

Has the server been rebooted?
NVITEnd-user supportCommented:
The error is from an application?
Can client access share via Windows Explorer?
Try resetting the computer object on the 2003DC then re-add the computer to the domain again.

10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

RBEdwardsJrAuthor Commented:
Arnold, changed the computer name through Control Panel>System and Security>System - Computer name, domain and workgroup settings. The 2008 server shows no sessions and no open files.
RBEdwardsJrAuthor Commented:
NewVillageIT, the error is received when attempting to access the share through windows explorer. Trying to access the share in order to install the application.
JohnBusiness Consultant (Owner)Commented:
On the problem computer, run TCP/IP Reset and DNS Flush.

Open cmd.exe with Run as Administrator
Then  netsh int ip reset c:\resetlog.txt
Also, ipconfig /flushdns followed by net stop dnscache followed by net start dnscache
Then restart the computer

See if that helps.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RBEdwardsJrAuthor Commented:
Krompton, while the client was removed from the domain, I deleted it through server management on the SBS2003 DC  and also confirmed that it was no longer listed in active directory . I added it back to the domain using the wizard under Control Panel>System and Security>System - Network ID. So I think that would have already accomplished what you are suggesting, wouldn't it?
Yes it would. Sorry.
JohnBusiness Consultant (Owner)Commented:
If you tried DNS Flush to no avail (just a suggestion), then make a backup of the user account on SBS2003, delete the account and make new user account.
Is this an AD environment? The change might still use the old account under a different name.

In an AD the way to change the name deals with using netdom command line tool.

Which location within the AD is the system now in?
On the client,
Net use y: \\servername\sharename

What is the error ID?
Natty GregIn Theory (IT)Commented:
when you change the computer name did you put back this computer into its original OU under computers
Is this new rogue device is authorized to use the system resources

in a domain setup user and computer must be authorize to use system resources, if the user is authorized but not the device in which they used to access system resources then its a no go

also check your error logs it usually points you in the direction of the solution
JohnBusiness Consultant (Owner)Commented:
@RBEdwardsJr - Thanks and I was happy to help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.