March 31, 2005

Curious George: Big Netowork/Server Problem Note to self: Studying for the MCSA does not equal expertise with servers. please help

Here's what I did: - Logged onto another computer with my account in order to access the K drive - On mapping the K drive on this computer, I found I had to enter a PW to get in, and oddly the PW wasn't the one I use to log in, or any other PW I know of - Decided to check it out at the server, saw that the K drive (the specific share) doesn't show up ANYWHERE on the server. Odd, to say the least, since it's seated on the network - Bad move #1: Mapped the K drive on the server, finding it's not at all what the K drive should be. - Bad move #2: Managed permissions for this odd K drive, hoping that the real K drive is in there somewhere. Added "Administrators" and only that group to permissions (K is our "sensitive data" drive) - On the computer I was logged in at, I mapped the K drive - K drive STILL isn't what it's supposed to be. Very, very confused now. - Disconnect from this odd K drive on the other computer, and on the server - Now is where I get that horrible feeling in the pit of my stomach - Run to my computer, and sure enough, can't access the K drive. Access denied. Our contract computer support people can't be here for another 2 hours, and while we can make do, we'd rather not. Any ideas?

  • Erm, now I can't spell. Network, the title word should have been. :o(
  • Hi Minda, I'm not sure I get this, so bear with me. The K drive is on the Server, right? So it is a directory that you assign the "K" label to and then it is also shared as the "K" share on your net. Right? What do you mean when you say that you, "Mapped the K drive on the server, finding it's not at all what the K drive should be." This is not clear to me. If you have admin rights on the server with the content, get on the server and search for the files that you know are in the "K" drive. Scope out what folder contains all that. Add a new share and then go see if you can attach to it from a remote machine. Then go back and clean things up to a point where everyone can use it. Else, you have more general troubles or a misstep along the way. Let me know
  • So is the "server" you mention the one hosting the share? You should be able to find it on there using the shared folders MMC snap-in (or from computer management by right-clicking on My Computer and selecting Manage)... if it's not there, then something sounds very wrong (particularly if there's another share by that name on the network).
  • You guys, the extent of my stupidity is such that I actually tried to map a network drive... on the network! I honestly don't know what I was thinking, if at all. I'm very afraid that I've replaced the original K drive with something totally different. I just pray that last night's backup will be able to fix it, should it come to that. But it turns out there is a drive called K, and instead of our financials, it has a lot of Windows Update uninstaller files, and so on. I have no friggin clue where it came from. I'll go try the MMC trick now, thanks uncleozzy.
  • Eh, there goes that idea. We've got an old version of NT SBS running our server, and it's got nothing in the way of MMC snap-ins. Since I've had to move on to another task, I can't go searching for them now. Blech. I simply can't believe I did this. It'll be one to remember, all right.
  • * wishes he had power of VNC * this is nothing to panic about; Sounds like a problem with naming conventions. I don't see how there would be data lost, save restoring a backup and losing the work from today.
  • "the power of VNC" like caveman sigh.
  • I just did a search as masked lurker recommended (thanks; I'd have not thought of that), and I can't locate any of the files. Makes sense, as not being able to find the share in the first place is what started all this (and then my bright ideas made it oh-so interesting). Not sure what naming conventions are, Allesklar, but I do appreciate the vote of conifidence ("nothing to panic about").
  • How many servers do you have? Do you have any machines that still have the "k" drive mapped?
  • Ah, NT ... I seem to remember there is an easy way to see which folders are shared on NT machines as well, but I can't remember it, and I don't think I've got anything running NT left in the office. Sorry... On the upside, though, I agree: this is nothing to panic about.
  • Just one server, and the computer I'm on now has the drive mapped, although Access is Denied.
  • Ah, thank you, uncleozzy! Two votes for "don't panic", and only my own paranoia (and embarrassment & humiliation) votes for "panic" ;o)
  • Have you made any changes to this machine? You are still logging into the computer with a domain right? You're not logging into the computer "locally"
  • No changes. Yep, logged in with a domain, not locally. Also, the other shares on the network, the H & G drives, are still accessible.
  • These are on the same server yes?
  • Yes.
  • What sort of hardware is the server running on? Have you checked through the Event log (probably in System) to check for any "warning! danger! hdd about to poop its pants!" messages?
  • Ah, I sure haven't. I'll do that now. (not sure what kind of hardware, other than whatever was mid- to bottom-of-the-line in 2001/2002)
  • Uh, isn't it supposed to be MCSE?
  • legumemotivator: nup. MCSA (4 exams) is the MS Certified Systems Admin - the mid-tier qualification between MCP (1 exam) and MCSE (7 exams)
  • Also - I'm sitting in #mofirc (for a bit, anyway, until the boss gets in) which might be an easier place to help you trouble-shoot.
  • Ditto
  • Ditto
  • coriolisdave: looked through the logs, and found only 2 information entries that may relate (they happened before I worked my magic): "The server was unable to add the virtual root '/PrxDocs' for the directory 'C\WINNT.SBS.\help\proxy' due to the following error: The system cannot find the path specified." and: "The server was unable to add the virtual root '\Administrative' for the directory 'D:\Administrative' due to the following error: Access is denied. The data is in error code." Administrative, or Admin$, is the name of the K drive. p.s.(apologies for typos, but no time to fix)
  • Try sharing it as something else, anything else? Bob$?
  • the account you have has domain admin priv's? If not, and you have "root" access, create a new user with full admin rights; Login to the PC and try mapping again.
  • Okay, tried that, and the "new" K drive came up - the one with sys & Windows Update files. Eek!
  • I have #mofirc open, but nobody's home...
  • Okay.. let's take a step back here. How exactly are you trying to map these drives? When you did the search before, you were on the server, yes/no? If so, and if you didn't find the files, there could be an issue. You can't map what isn't there.
  • Ok; are you sure you've done an exhaustive search on the server for the files that should be in the directory (I'm not trying to patronize); additionally, do you have an external backup appliances? Is it possible there is another machine on the network that the drive was mapped from?
  • Well, when I mapped the first time, it was through the basic folder view -> tools -> map network drive. Yes, the search I mentioned above was on the server. However, I've been using/on the K drive all day with no problems, and am positive that I didn't delete it. On preview: Yep, searched for several different files, and checked my Windows Explorer, which still shows the K drive, for exact spellings. No dice. The drive couldn't have been mapped from somewhere else - we're a micro-company with only a few computers and the one server. We don't even have a proper network, just 7 computers connected to the server. On re-reading your question, there's an internal Seagate backup device.
  • Backup device? I am assuming it is a tape drive. Have you looked in the recycle bin? It seems very odd that a directory would come up "missing" Ok; when you click on the "k" drive on the server (right click) what is in the description? Does this say "Admin$" or is it something else? Maybe a computer name?
  • Yes, it's a tape drive. The share wasn't showing up from the beginning, so there's no clicking it. And there's nothing in the recycle bin. (if I sound snappy, I apologize. I really appreciate the assistance; just a bit stressed out between breaking the server, the one deadline that requires K drive access, and the other deadline which requires me to do something completely different. Bad, bad day).
  • What are the properties on the share-which-no-longer-works? How is it mapped in your logon script?
  • Ah, well, hm. I'm afraid I don't know, and, well, hrm. I don't know how to find out. *cries, then remembers it's time for a cigarette, then thanks God the decision to quit was put off till next week*
  • Ok... I think what is important here is to understand >WHY< you are trying to map a drive on the server; You have one "server" several clients; It makes no sense that this folder would be "mapped" this is a local directory that is shared, so clients can use access that directory. The clients have mapped drives, pointing to a shared directory on the server; If you cannot find said files on the server, I'd search the other 7 odd machines, in lieu of someone setting up some wacky network, long ago.
  • Um. The script should be a batch file, and I think is listed under the properties of the username in User Manager. So basically, log on to the server and have a poke at them? (Sorry - I'm a 2k/2k3 admin, never really worked with NT)
  • Allesklar, exactly. My decision to map the K drive on the server was a stupid one, because the server is where the K drive resides. My one saving grace is that the share was missing before I poked around & messed it all up. coriolisdave: I'll give it a go. The computer guy should be here within a half hour... I'm hoping I can fix it before then, because I'm going to be the one paying for his time. Blech.
  • Chin up Minda - the only way to learn this shite is by blowing things up ;)
  • Is it unusual that my own user account isn't listed in the Local Users & Groups snap-in on my machine? going to the server now...
  • Update: I found the share! however, access is denied to the folder from the server.
  • No.. your Domain username is stored on the DC, not locally. It is useful, however, to have your Domain username listed in the Local Administrators group, so you can install stuff. This will not effect your Domain access, however.
  • Bollocks to that. You should still be able to change the security/permissions settings on it. OR Change the permissions on the folder which contains the shared folder (i.e. c:\, for c:\share\) and set the perms to inherit.
  • We're getting warmer ...
  • Eh. Went though the permissions routine a few times, got access to Admin, however subfolders aren't accepting the new permissions. Going to try to map the K drive on the other computer now...
  • Bah, the other computer still connects to that weird "other" K drive on mapping.
  • net us k: \\server-name\folder
  • ahem. net USE
  • Yeah, that's the way I did it.
  • try mapping it to q: or similar, instead.
  • I'm a bit afraid to try this out on my own computer, although it doesn't matter at the moment since I still am denied access to all K drive folders. Curiosity is saying do it, but caution is saying no. What do you think?
  • Also, if you haven't already - try just logging off and rebooting.
  • Sorry - try what?
  • I mapped it as E on the other computer (comes up by default when Tools->map network drive is selected), and got the same odd folder with system/Windows Update files.
  • Sorry - try mapping it on my own computer. But as I said, it's not an intelligent question, because I can't access it anyway.
  • Restarted, access to K drive is still denied...
  • When you're mapping it, are typing the command from the "run" box or a command prompt? If the latter, does it provide any feedback after execution? If the former, try the latter? :)
  • When you are mapping the drives through the menu, you are picking a specific folder no? The folder that you fixed the shares on? Try giving access to "everyone" see if that fixes the problem then work backwards
  • (showing my true non-depth of knowledge:)What's the command for that, please?
  • It's quittin' time in Chi-town; Good luck! BTW, if this info is so critical, you might consider an alternative backup solution to your tape, and try and pull the info from the tapes, I'd wager this hasn't been tried in a while and tapes get "crusty" Peace, AK On Preview -> Right click the shared folder(s)on the server add the user "everyone"
  • was that the command you were after?
  • Computer guy is here, and he's not even sure what the hell I did. We're slowly but surely getting access back... Thanks for all the help!!!!
  • Well, computer guy was here for an hour, manually fixing the permissions. While I was trying to get access back to that share, I had changed the permissions in a drastic and inconvenient way. We still don't know what the deal was with that "other" K drive. He's coming back next week to make sure it's still all OK. Before he left, he gave me "The Look" and said, "Your fingerprints are ALL OVER these files". I could only hang my head in shame and admit I shouldn't have touched anything. Again, thanks for coming to the rescue. We'd nearly had it before he got here, which is a feat considering it took him an hour in person to figure out how to sorta fix it, and still doesn't know quite what it's all about. See you all Monday! :o)
  • I'm feeling extra sexy today. and my hair looks really good.
  • Yo Minda? The correct expression is "bare with me..." And we know what happens from there.