Restricting access to one user on a workgroup

  • Thread starter Thread starter Richard
  • Start date Start date
R

Richard

Hi,

I've been trying to make a Win2003Svr/SP1 share available to a user on
a WinXP-Pro/SP2 workstation networked as a workgroup rather than a
domain.

On the server, I tried to identify the user as
WorkstationName\UserName, but the server said something like "location
unknown."

Then I tried to select the workstation from the "Locations" dropdown
combobox on the server, but only the server itself was listed there.

I don't want to give "evervybody" total permission for fear that
someone can hack me to death via the internet. Do I have to switch to
a domain to achieve my purposes?

TIA,
Richard
 
create a user a/c + password on the server and use those credentials when
accessing the share from the client PC.
 
Hi Gerry,

Now that you show me the path, it's obvious :-) Isn't that the way
life is so often? Thank you very much.!

Best wishes,
Richard
 
No Problem Richard, glad I could help.


Richard said:
Hi Gerry,

Now that you show me the path, it's obvious :-) Isn't that the way
life is so often? Thank you very much.!

Best wishes,
Richard
Click to expand...
 
One more question, Gerry:

I created a new user on the server whose:
-- name is unique on my LAN;
-- membership is the Administrators' group

I created some shares on some Server 2003 folders. In each case, I
deleted "Everyone" and gave full permissions to this unique
administrator.

By mapping drive-letters to the various shares, I seem to be able to
craeate, modify and delete foldrers and files. But it seems that if I
hibernate/restore the workstation while the server is down, I'll lose
all those mappings. That makes this approach less than ideal.

Is there a simpler way around the drive_letter approach? I'll settle
for this if I don't learn a better trick :-)

Best wishes again,
Richard
 
Are the mapped drives actually disconnecting or do they just appear with a
red X over them? If its the latter then you should still be able to access
them. If its not I'm not too sure why thats happening, we don't use
hibernation here, + all PCs are on a domain.

You could always use shortcuts to the shares as opposed to mapping them?
Browse to the share --> right click and create shortcut (think it puts the
shortcut onto the desktop)

hth
gR
 
Hi Gerry,

Everything's working great. Like Chicken Little, I was anticipating
the "sky would fall" after I shut the network down.

As it happened, I only mapped one drive letter to a server share, and
it was persistent as long as I rebooted the server first and the
workstation subsequently. (I don't know if that order is a
requirement; nor do I care.)

In fact, I wound up deleting the mapping entirely and relied on using
the shares that show up under my workgroup in Windows Explorer. That
display is persistent.

Hibernation in XP and Server 2003 works great for my little network.
It restored the state of the systems at shutdown almost exactly and
disable the server's little documentation feature regarding unscheduled
shutdowns.

I textolled hibernation's virtues to my son, but he can't take
advantage of it. He works for a national organization that, like
yours, uses a domain and my son's not a domain administrator there.

So, again, thanks for your response. I think I can fly solo from here
on :-)

Best wishes,
Richard
 
Back
Top