Cannot perform File Server Recovery

[alohaakamai3]

I have not seen this one.

Terminal was placed into redundant mode due to unknown problem with the server. Minor changes were made to the server to get Aloha to communicate with the redudant terminal again. Previously, attempts at a File Server Recovery would do nothing. Now, I get a quick flash on the terminal that says "File server recovery... please wait" ... and I get this in the debout of that terminal:

Sep 11, 08:07:04 Recover from fileserver down requested... (Current server is 'TERM4')
Sep 11, 08:07:04 Attempting to connect drive Y: to server 'ALOHABOH'...
Sep 11, 08:07:04 Add connection Y: to \\ALOHABOH\BOOTDRV returns 5
Sep 11, 08:07:04 Recovery result is 0


Aside from maybe the abscense of a mapped drive (which I don't think it is) or a permission issue (can't for sure this isnt it, but nothing had changed and permissions look good) ... does anyone have any suggestions?

 

[bigblok403]

Return 5 = Access Denied

 

[alohaakamai3]

You're correct. Since I posted this, I have since narrow this down to a windows problem, which I have seen way back when, and there are a ton of posts on the Internet it- BUT, I have not been able to resolve it.

Tryng to access the bootdrv on the back of house from any of the Win98 SE terms yields a message asking for a password to connect to the IPC$ share. This is a share automatically created by windows.

1) I have reset the passwords on the front and back of house to what they were before: guest, with no password (real secure, huh? ). I've also tried creating other accounts on both the XP back office and the front of house terms--still get the windows error.

2) No idea what change this. Woke one morning to a MAKE FILESERVER, and it has not worked normally since.

Any suggestions would be appreciated.

 

[bigblok403]

I would think if it happened overnight that a passwords on the server would have expired or firewall turned on. I always hate when this happens. Try deleting and re-adding BOOTDRV share on the BOH and/or deleting .pwl files from FOH terminals, this sometimes works for me when I don't have time to figure out what happened. When it asks for the passwords and you put them in, can you connect afterwards? Also what O/S is the server?

 

[alohaakamai3]

Thanks for the suggestions, Bigblok.

I tired deleting the pwl files on the 98 box too. No dice.

I too, have also seen where the user account (especially the guest) is set to expire, and it behaves exactly like what I am experiencing now. So, good call on your part, but that doesn't seem to be the case this time. The accounts are set not to expire, have had the password reset on both the front and back of house, and are the same user name and password on the two machines trying to access one another.

Again, had the same thought as you on removing the bootdrv share, and resharing it--didn't work.

The back of house is XP Pro SP 2, 6 terminals running 9x, 5.044. As said, all the sudden--boom. No one can talk to the big daddy (Alohaboh).

I am really getting annoyed with this thing.

 

[alohaakamai3]

Oh, and just for good measure, I had given the GUEST account admin access on the XP box, just to make sure we weren't running into any funny business there.

 

[bigblok403]

Hmmm...Any windows auto-updates on the BOH. I guess at this point it could be anything.

 

[alohaakamai3]

Sorry, I am so scatter brained here, I not answering all of your questions. And you DID ask a good one:

No, come to think of it, I don't think I can access the bootdrv with what should be the proper password. I cannot check it this second to be 100% sure (remote access not available), but I am pretty sure I tried to manually enter the password, and it denied me. Did we just narrow the problem down here?

Although, the "glass is half empty" guy in me says "no", because we probably wouldn't be getting this message in the first place if windows thought the passwords were kosher (i.e. I probably could have assumed that it doesn't think the passwords are the same all along)

 

[alohaakamai3]

Just another little bit of info-- the end-user claims that accounts started to appear on the logon screen on the BOH around the time the problem started happening--that were not there before. Wish I had more specifics, but essentially he is saying there used to just be one user logon on the BOH when you dialed in, and now other users accounts that were on the system (but not showing up as an option to logon) started to appear.

I don't know if this has anything to do with it, but I figured I would mention it since I am about to call this thing off, and just reload the whole box. Obviously, I don't want to waste the time doing this for something that it probably a 60 second fix (when you know what it is), but I have already spent way to much time on it.

So, any heros who want to save the day on this one, now is your chance to shine?

Bo, Rokstar, Posrescure, BigBlok, ezcrane, Adam (I think he died, he hasn't been on here forever).. now is your chance to shine Sorry if I missed any other Aloha gurus....

 

[posrescue]

- Make sure firewall is turned off on FS
- Make sure the security settings on the fileserver will allow logon with blank password (default setting is console only in XP)
- Is the FS logging in with an administrator user name and pass? - If so try logging onto a terminal with that same user and pass
- Is bootdrv share set for full access to all?