Pro/Forums - View Single Post - Users can't access 4400

blue68f100 · 03-22-2007, 07:17 AM

Never had ran into that. Look at your connected user log, and see if it will give you and options. You may have found users are sharing user ID and PW's. And if your have anoymous FTP connection allowed, try reducing the max allowed. I would have guessed if a user was rebooting on a regular basis that would not have happen.

How much ram is in the 4400? def 256? Increase your ram in the 4400. Uses PC133 EEC registered ram. Re booting is just a temp fix. Send out a broadcast that the server will be rebooting in ## min, giving users time to close any files, watching the log you should have an idea of who's still connected. Or tell them it will happen after hours.

03-22-2007, 07:17 AM	#2
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: Users can't access 4400 - running at capacity.... Never had ran into that. Look at your connected user log, and see if it will give you and options. You may have found users are sharing user ID and PW's. And if your have anoymous FTP connection allowed, try reducing the max allowed. I would have guessed if a user was rebooting on a regular basis that would not have happen. How much ram is in the 4400? def 256? Increase your ram in the 4400. Uses PC133 EEC registered ram. Re booting is just a temp fix. Send out a broadcast that the server will be rebooting in ## min, giving users time to close any files, watching the log you should have an idea of who's still connected. Or tell them it will happen after hours. __________________ 1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820