Re: Basic Networking (filesharing)



On Wed, 25 Jun 2008 18:57:02 -0700 (PDT), Rene_Surop <infodynamics_ph@xxxxxxxxx> wrote:

Hi,

This is basically a networking issue though programs are written in
Cobol. The Cobol application uses a networked file as SELECT filename
ASSIGN TO "\\server\sharefolder\Users.DAT"

On the client-side, I still need to 'map' the networked sharefolder
with Windows OS username/password for the client PC to access it.

No you don't need to map a drive letter. You can access it as
"\\server\sharefolder\Users.DAT" without a drive letter.

But the mapping of a drive letter has nothing to do with security.

Once
the drive letter has been mapped and everytime the client PC logon...
the folder is wide open for access. Meaning it could be deleted by the
client PC (users). This is very risky.

There are a wide variety of permissions that can be granted by user and role, on
directories and on individual files. Using Explorer, right click on a directory,
Properties, Security, Advanced, (select a user), View/Edit. See all the permissions that
can be granted and denied?

Security is achieved by granting PERMISSIONS to users, not by denying them access to the
disk.

The network platform is simple and I do not use DFS (distributed file
system) in windows server. Did not use it because I only have one PC
server.

You are using SMB and Domain authentication.

How can I connect to the \\server drive "without" exposing the mapped
network drive? Can I probably use autoexec.bat or win.ini file to
connect to \\server without exposing (naming it drive H) it as mapped
network drive? The client PC uses Windows OS.

Drive mappings can be set to automatically reconnect. You shouldn't put them in
autoexec.bat or win.ini. You're not running MS-DOS. You don't need mappings unless you
want the shared directories to appear in Explorer.

If you want the application to have different permissions from users (why?) start them
using runas:
runas /profile /user:(server)\(user) "(yourprogram)"

Your users will need to know the password for (user), so they could run the above with
(yourprogram) = cmd, or do their own drive mapping.
.



Relevant Pages

  • RE: Lost my outlook contact... :(
    ... the network configuration is started from a web page located ... client computer, you will see a welcome page to invite you to start the ... local user profiles to the domain user profile. ... Before joining client computers to the network, ...
    (microsoft.public.windows.server.sbs)
  • Re: SMS 2.0 and SMS 2003 Running at same time in same domain.
    ... the clients are on the network. ... The operating system reported error 53: ... Possible cause: The client is offline. ... Verify that the client is connected to the network and that the SMS ...
    (microsoft.public.sms.setup)
  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Wireless Security Notes and Findings (from this list and other places)
    ... There are two general areas of wireless security: Authentication and ... authentication standard that works with wireless networks. ... client computer runs a client program to connect to the network with a ...
    (Security-Basics)
  • Re: Small business thinking about backing up data, having a server and 2-3 users - is SBS200
    ... is networked to the Master with a crossover network cable. ... Master on the Master PC and Client on the Slave pc. ... Since this machine is a server is should handle the requests ok ... Most real firewall appliances have HTTP and SMTP proxy services that allow ...
    (microsoft.public.windows.server.sbs)