Need some help with Server 2k3 re: permissions

[Ns1]

I can't for the life of me get this file sharing to work and I have no idea why.

Here's the setup

OldServer and NewServer

Local user/groups only, no domain, hell no access restrictions to speak of.

I have a folder on NewServer I'm trying to share. I more or less copied all of the local user info from OldServer to NewServer into a group called DefaultGroup, with full permissions.

I set up the share, and then in the folder permissions button, I add DefaultGroup. Then I went to the security tab and added DefaultGroup.

Now, all computers can ping NewServer. When I try to map the network drive (from a workstation), I can see NewServer, but when I double click on it, it gives me an "access denied, you may not have enough permissions to access the requested object" kind of message.

However, when I'm on OldServer trying to access NewServer, it works fine. To further test things, I plugged in my laptop, added myself as a user to both servers, and I can access OldServer but not NewServer.

Any ideas?

//edit

I've tried this with windows firewall on (with exceptions) and off and neither has worked.

 

[imported_snikt]

What OS are the clients using?

 

[Ns1]

Originally posted by: snikt
What OS are the clients using?

XP all around, some pro some home.

 

[Pantlegz]

Are the account names the same? I was always told if the account names aren't the same (ie: admin, not the display name) then file sharing wont work. I've had a similar issue and honestly don't remember how I fixed it. Maybe put all the users in the same group on both machines and it tricks it into thinking it's the local machine attempting to access it... I honestly gave up on windows file sharing without a domain, it works sometimes and doesn't others with no reason as to why it wont work.

 

[kevnich2]

How many user computers do you have? You should really think about having a domain setup. The client user account (username and password) have to be identical to that of the server user account that you've allowed access. If the client computer ever changes the password, they won't be able to get on the server.

 

[Ns1]

Originally posted by: kevnich2
How many user computers do you have? You should really think about having a domain setup. The client user account (username and password) have to be identical to that of the server user account that you've allowed access. If the client computer ever changes the password, they won't be able to get on the server.

We're talking 12-15 machines here. There's too much work and too little budget to properly implement a domain.

There are NO passwords on any of the workstations...


I mean theoretically, this is ALL I need right?

Username on computer = User (object in Local Users)
Add permissions to folder + security permissions
NO firewall obstruction

And if the computers can see the server, this SHOULD work right?

It's really bizarre to me that OldServer can access the folder, but the computer that I plug into the network with known good settings can't.

 

[drebo]

Not too much work, imo, and well worth it.

12-15 machines? Should only take about 8 man hours, and using the Files and Settings Transfer wizard in XP, you can move user settings over easily.

 

[Ns1]

Originally posted by: drebo
Not too much work, imo, and well worth it.

12-15 machines? Should only take about 8 man hours, and using the Files and Settings Transfer wizard in XP, you can move user settings over easily.

That's 8 man hours that I'm not gonna get paid for, but I'll consider it...

 

[kstornado]

Originally posted by: Ns1

Originally posted by: snikt
What OS are the clients using?

XP all around, some pro some home.

I would suggest setting up a domain as well, but you'd also have to tack on the time to upgrade the home users to pro, as XP home cannot join a domain.

 

[yinan]

There is a default security policy in place on the server that prevents accounts with blank passwords from connecting.

 

[Nothinman]

That's 8 man hours that I'm not gonna get paid for, but I'll consider it...

And how many hours have you spent on this migration and troubleshooting this problem already?

There is a default security policy in place on the server that prevents accounts with blank passwords from connecting.

That's most likely it.

 

[Ns1]

Sonuvabitch!

Is this it?

What to do
Windows XP Professional, Windows 2003 member server

To enable the use of blank passwords

* select Start|Control Panel|Performance and Maintenance|Administrative Tools|Local Security Policy
* select Local Policies|Security Options|Limit local account use of blank passwords to console logon only
* select 'Enabled'
* click 'OK'.

Windows 2003 domain controller

To enable the use of blank passwords

* select Start|Control Panel|Administrative Tools|Domain Controller Security Policy
* de-select 'Local Policies|Security Options|Limit local account use of blank passwords to console logon only'
* enable 'Define this policy setting:'
* select 'Enabled'
* click 'OK'.

If you need more information or guidance, then please contact technical support.

 

[kevnich2]

For your system, I highly recommend a domain setup. Your going to spend more time troubleshooting your current system than you will by just setting up a domain and having it work like it's supposed to.

 

[Ns1]

Originally posted by: yinan
There is a default security policy in place on the server that prevents accounts with blank passwords from connecting.

You sir are my hero. I disabled the security policy today and everything worked fine.

Thanks!