- Oct 23, 2000
- 9,200
- 765
- 126
I apologize that this initial post will be lacking some details but I want to get it started to see if anyone has any suggestions before I am able to actually physically access the server in question.
I want to preface this by saying that I don't normally do much with servers. I primarily support desktop systems and physical/wireless networking, but I was "elected" to be the tech guy for this small office mainly because my wife and her sister both work there. I can usually handle the infrequent problems that come up, but I don't have any idea where to even start with this one.
A small office consisting of about 20 Windows 7 Professional workstations connected to a Server 2012 Standard R2 server in a domain. This server replaced an old SBS 2003 server about two months ago. Everything has been working great up until today. Now all workstations on the network are unable to access any shared resources on the server including shared network printers. When attempting to access their mapped network drives (or directly access any \\servername resources) they get an error message that says "Microsoft Windows Network: Logon Failure: The target account name is incorrect." The network drives are mapped automatically by the login script to \\servername\sharename (with the correct info for the appropriate shares and drive letters). Shared printers all show as "offline" on the workstations.
I have found quite a few reports of this error online, but the only suggested possible causes in any of those postings are that this is due to incorrect replication between multiple servers on the domain and to repair the replication process. But this is the only server in this office so there isn't any replication involved.
Nothing has been changed on the server in at least a month (I installed some Windows updates then) and nobody knows the server admin password except me and my wife, and she hasn't touched it at all since it was set up. She only has the password in case of emergency.
I have LogMeIn installed on the server so that I can easily access it remotely as needed since I don't actually work in that office, but when I enter the credentials to connect to LogMeIn, the system says "Invalid username or password. Verify and try again." even though the credentials are definitely correct. This happens whether I use the normal working admin account or the built in Administrator account. I'm not certain that this is related, but I did first notice the problem when I tried to log in to the server to find out why the users were getting the target account name errors.
I discovered that I can successfully map a network drive and access the contents of the drive from the workstations if I use the server's IP address instead of the UNC name, and that is a partial and temporary fix, but not a real resolution since some of their programs rely on the UNC name and it doesn't really fix the root cause of the problem.
Any ideas what might be causing this, and how to fix it? Or anything I should look for when I am able to get to the office and have physical access to the machine tomorrow?
I want to preface this by saying that I don't normally do much with servers. I primarily support desktop systems and physical/wireless networking, but I was "elected" to be the tech guy for this small office mainly because my wife and her sister both work there. I can usually handle the infrequent problems that come up, but I don't have any idea where to even start with this one.
A small office consisting of about 20 Windows 7 Professional workstations connected to a Server 2012 Standard R2 server in a domain. This server replaced an old SBS 2003 server about two months ago. Everything has been working great up until today. Now all workstations on the network are unable to access any shared resources on the server including shared network printers. When attempting to access their mapped network drives (or directly access any \\servername resources) they get an error message that says "Microsoft Windows Network: Logon Failure: The target account name is incorrect." The network drives are mapped automatically by the login script to \\servername\sharename (with the correct info for the appropriate shares and drive letters). Shared printers all show as "offline" on the workstations.
I have found quite a few reports of this error online, but the only suggested possible causes in any of those postings are that this is due to incorrect replication between multiple servers on the domain and to repair the replication process. But this is the only server in this office so there isn't any replication involved.
Nothing has been changed on the server in at least a month (I installed some Windows updates then) and nobody knows the server admin password except me and my wife, and she hasn't touched it at all since it was set up. She only has the password in case of emergency.
I have LogMeIn installed on the server so that I can easily access it remotely as needed since I don't actually work in that office, but when I enter the credentials to connect to LogMeIn, the system says "Invalid username or password. Verify and try again." even though the credentials are definitely correct. This happens whether I use the normal working admin account or the built in Administrator account. I'm not certain that this is related, but I did first notice the problem when I tried to log in to the server to find out why the users were getting the target account name errors.
I discovered that I can successfully map a network drive and access the contents of the drive from the workstations if I use the server's IP address instead of the UNC name, and that is a partial and temporary fix, but not a real resolution since some of their programs rely on the UNC name and it doesn't really fix the root cause of the problem.
Any ideas what might be causing this, and how to fix it? Or anything I should look for when I am able to get to the office and have physical access to the machine tomorrow?
Facebook
Twitter