Windows Networking thru vpn tunnel

[TonyB]

Hi,
I've connected up my home network to work via a ipsec tunnel. I can ping
machines either way, and I can make network connections from one side of the
tunnel to the other side. My main problem now is sorting out permissions.
Our work network uses an NT4 server domain controller.
At home I have a peer to peer network.
When I try to connect to a work machine from home by mapping a drive "net
use m: \\ipaddress\share mypassword /user:imageproc\myusername" the drive
is mapped but the files on the target machine are read only, although I have
used my usual passwords that I would use at work ?
Is there anything else I need to do to make this work ?
Regards
Tony

 

[Herb Martin]

Hi,
I've connected up my home network to work via a ipsec tunnel. I can ping
machines either way, and I can make network connections from one side of the
tunnel to the other side. My main problem now is sorting out permissions.
Our work network uses an NT4 server domain controller.
At home I have a peer to peer network.
When I try to connect to a work machine from home by mapping a drive "net
use m: \\ipaddress\share mypassword /user:imageproc\myusername" the drive
is mapped but the files on the target machine are read only, although I have
used my usual passwords that I would use at work ?

The one you use AT that machine which provides the
files?

If so the answer is almost certainly that your SHARE
is set to READ for you.

Change the share permissions (next time you are at
work.)

Is there anything else I need to do to make this work ?

Share permissions set an effective maximum for
ANY file on that share: Read, Change, Full Control.

You still need the appropriate NTFS (file system)
permissions but without the roughly equivalent
SHARE permissions you will not be able to exercise
those file (NTFS) permissions.

For example:
With READ at the share, you will be able to read
(some) files.

 

[BP]

Not sure if this will help but have seen same in the
past with non rras dialup servers.
Try to join the domain context with the workstation
service. In other words your workstations work group needs
to be set to the NT domain context of your work domain.
Try logging into your workstation with same
username and password as you mention would make win98
browser maintain a list of all your servers in the Neibhood
and not prompt for user/pwd once cached, at least it behaved
this way in win98 not sure about Xp clients.

 

[TonyB]

Hi BP,
I'm using win2k at home, I assume the same advice applies. I will try to log
onto the domain as you suggest.
Thanks
Tony

 

[TonyB]

Hi Herb,
After I posted I thought about trying to log onto my machine from another
machine at work using a mapped drive. As you suspected I don't have write
permission on the share.
I presume I can add write permission for my user name for the share ? I'll
try it at work later.
Thanks
Tony

 

[Herb Martin]

Hi Herb,
After I posted I thought about trying to log onto my machine from another
machine at work using a mapped drive. As you suspected I don't have write
permission on the share.
I presume I can add write permission for my user name for the share ? I'll
try it at work later.
Thanks

Sure. Anytime we can help.