• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Ouch called MS at $245.00, Win XP Pro permissions questions, i cannot get to the server!

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Originally posted by: SLEEPER5555
jonmullen = I tried the matching user names and it still did it, i really think carp has the right idea i just will see if how he says to do it is actually how to do it.

Fuzznuts = If carp is correct i am more than happy to pay $15 to him, if he is not and you are than i expect you to take the $15 or let me buy you a giftcard for $15 somewhere or something like that!
Click to expand...

did you match up the passwords for them too, and remember to add the user to both the network and NTFS permissions?
 
Ok get this! I call MS and they immediatly answer the phone i give them a brief overview of my problem they ask my name, phone #, CC#, tell me it is going to cost me $245 and charge my CC, immediatly i am sent an invoice by email for the amount, then they transfer me (i thought the first guy was a tech apparently he is just billing) so i am sitting on hold and after 20 min's i had to hang up because i had a meeting, so basically so far i have paid $245 to hold 20 min and get a trouble ticket #. So now later tonight i will need to call back and hold and hold an hold until i get an answer and a resolution. GOD I HATE THIS!

mboy= i put that in there and set it to 17 and nothing, it still tells me no way jose! I really thank you for the help (and the others)

jonmullen= it does not work!

I have been able to duplicate the problem on my home XP pro Network so i can call MS from here and get this issue fixed i hope! It is really easy to duplicate, this has to be a bug there is no way it was intended to be this way!

now it is just going to be cheaper to use MS, this issue is starting to cost me money and i am looking like a freakin idiot in the office. hehe ohh well!
 
Man I wish I had that kind of money to throw around.

Never call a tech support line if you have to be off the phone in 20 minutes.

I still think its a waste of money, and when you get a solution you will most likely find that it was in the knowledge base.
 
STaSh = i do not have money to throw around i just need a reso and i needed it today, my company is doing the IT work for this other company, they are the one's who have the server and now want it secured. so while i am paying for it they are really indirectly paying for it. They pay me alot to take care of this stuff so i cannot look like an idiot and have to get it taken care of reguardless of the cost asap, i am just glad they basically understand so it is not seen as my error and they do not drop my companies services. This is part of what i do to make $$ to pay my bills so one way or another it has to hapen. does that make sense?
 
Why don't you just do a 'net use x: \\server\share /user:server\username /persistent:yes'

That way you will know that you are using the right credentials. If it asks for a password, then you should be good. If it doesnt, then your permissions are screwed up on the 'server'

Also, only set permissions to shares using NTFS. Leave the share permissions at the default Everyone:Read.
 
not much help , but this is very simple using SAMBA and linux 🙂



can you delete all users except administrator on the server box?
then add a SEPERATE user/passwd for each client box?
set the permissions of the individual folders, etc.
 
Originally posted by: mcveigh
not much help , but this is very simple using SAMBA and linux 🙂



can you delete all users except administrator on the server box?
then add a SEPERATE user/passwd for each client box?
set the permissions of the individual folders, etc.
Click to expand...

or by just getting real server software to startwith, never run a baseline os for a server if you plan or suspect security of anykind will be needed. peer to peer just isn't made for that.
 
Just be careful that they know what they are getting - A Windows XP box isn't meant to be a server, and you're missing a *lot* of security features and capabilities that you'd get with a real copy of Win2K.

Also, XP has an inherent limit in the number of connections that it will accept - You won't ever get more than ten computers to connect to it at once, so your client has NO growth potential. No to mention that they can't all have their computers connected at once without running into problems. Actually, the number of inbound connections is ten - It's possible that some computers might use MORE than that, even under normal circumstances.

The details can be found

in this article at Microsoft.

- G
 
Originally posted by: Garion
Just be careful that they know what they are getting - A Windows XP box isn't meant to be a server, and you're missing a *lot* of security features and capabilities that you'd get with a real copy of Win2K.

Also, XP has an inherent limit in the number of connections that it will accept - You won't ever get more than ten computers to connect to it at once, so your client has NO growth potential. No to mention that they can't all have their computers connected at once without running into problems. Actually, the number of inbound connections is ten - It's possible that some computers might use MORE than that, even under normal circumstances.

The details can be found

in this article at Microsoft.

- G
Click to expand...

The same thing goes for Windows 2k unless you get 2k server. Anyway I really think it is a credintials think and the way XP tries to send them. Stash has a good idea that will help you narrow down the problem. Try it and get back to us, or tell us what M$ said
 
Garion=yes i have pointed that out to them and they have about 7 ever connected so they do not see it as a major issue right now (even though one comp can use two connects) . My guess is that soon they will be wanting to setting up a new box that will run 2k or 2k3 because they are growing very rapidly right now, so XP pro will not cut it soon.
 
DId u reboot the box after the registry change?

Yep, going to a real serrver OS instead of a desktop OS would be the smart thing. NO offense, but you nor your co. should have even reco'd XP for a server, especially if you are getting paid to do so.
 
mboy- yes it was rebooted after, the reason they used XP Pro for the server was because they were small just a few months ago and had a max of 4 people connecting to the server so it worked well. They have grown far faster than they thought they would and now suddenly are at the limits. Another reason they went with XP was costs at the time were the biggest issue. We discussed it last night and in about a month they want me to build a new server (a real one) 2 gigs memo, RAID, 2K or 2K3 server. etc. the existing server will be recycled as a client box so no money was wasted!

previously they were using a P2 running 98SE as their server because they had no computer knowledge and they just bought some cheap comps and linked them and NO AV software at all!!, hehehe (<- all this i had no part of)

So 2K or 2K3?

Oh and i still have not had time to call MS, i will do it tonight and let you all know the expensive fix!
 
Sleeper5555, I had the same problem and was tearing my hair out. I thought I was the only one having that problem. It would ask for a password if I tried to login from a XP machine to a Win2K machine, but wouldn't if I used an XP machine to login to an XP machine. So if you can use Win2K, I'm almost sure it'll work the way you want it.

I did end of solving it, but I can't remember how I did it. I messed with a lot of things. Since I have formatted and lost those settings. I'll try again when I get home, but I'm not sure if I can redo it. And I won't be home for a while as I'm at work.

I feel your pain, this really really ticked me off as if you do everything the same in Win2K (except turning off Simple File Sharing), it would have worked in Win2K.
 
i think jonmullen had it right .
say you have 3 people - each one needs to create a user account on the server with their own name and password. then you can login as admin and set permisions for each user with what ever shares you need.
that way the server comp , which is a LAN as pointed out , not a real "server" , will just allow everyone to login remotely to whatever they have been given accsess.
good luck
 
But I think Sleeper5555 was trying to do what you could do in Win2K, logon to the remote box using an account from the remote computer. This was possible in Win2K without a client/server model.
 
Originally posted by: STaSh
Um...one more time: Did you try my suggestion?
Click to expand...

Try the man's suggestion. I will really help us find out your problem...I still think XP by default is sending the current users name and pass and if you dont have that setup on the other system it wont work. This way you can send another username for sure. This is probably just a case of something M$ thought would be a good idea but ended up being a major PITA.

In short try the man's idea.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top