Re: Copy to Mapped Networked Drive Error

The choice of operating system, workgroup name or username for the
workstation is not mine. I understand the effective permissions, but your
observation is usefull for others; if this user connects remotely, he has
full control of his workspace. I typically remove everybody as a user group
from share permissions and assign explicit rights.

This unit has a dynamic ip address WAN wireless connection to the Internet
via the PPP adapter. I am assuming the MAC Bridge Miniport is part of the
configuration as this device may support a different communications protocol
(i.e. ATM, X.25, Ethernet, etc.).

I'm not sure if this workstation is or is not part of a home network; but
since the primary function of the browser service is to provide a list of
computers sharing resources in a client's domain along with a list of other
domain and workgroup names across the wide-area network (WAN), I'm not sure
disabling it makes sense here.

Thanks for the suggestions.

Marc


"Lanwench [MVP - Exchange]" wrote:



In news:622320B0-20C1-4EEC-99F2-35DB8857581E@xxxxxxxxxxxxx,
alaskanrogue (Marc George)
<alaskanrogueMarcGeorge@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Scenario:

XP Home Edition SP2 with basic workgroup, user logged on as owner with
mapped drive using different user name to 2003 Server SP1 shared
folder over the net. Able to browse but unable to copy to shared
drive without error "Error Copying File or Folder. Cannot copy xxxx:
Access is denied. Make sure the disk is not full or write-protected
and that the file is not currently in use." Domain user has explicit
full control permissions on folder and is member of Authenticated
Users which have modify permissions on share.

FWIW, I usually leave share permissions as everyone=full control, as it
makes life easier. Note that even though you've granted this user Full
Control all he'll effectively get is Modify.


Using different computer with XP Pro SP2 but computer as member of
domain on local network, logged on locally, i.e. not as domain user,
but same drive mapping parameters including domain User ID when
mapping drive, no problems.

Suggestions?

Outside of the obvious, which is "upgrade all XP Home boxes to XP Pro and
join the domain", I'd probably make the local computer username & password
identical to that on the domain, and perhaps even make the workgroup name
the same as the domain's NetBIOS name and see if this still happens. Also
see more comments below....


Marc

PS: Based on other posts, the ipconfig and browstat for the problem
computer are:

Windows IP Configuration

Host Name . . . . . . . . . . . . : LIFEBOOK
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Network Bridge:

Remove this...you can't possibly need it in this context (unless it's used
elsewhere, but I find that unlikely).


Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : MAC Bridge Miniport
Physical Address. . . . . . . . . : 42-D4-13-65-AB-D0
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.209.71
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

PPP adapter Sprint PCS Vision - Novatel Wireless:

How is this computer actually connected to your network? I'd disable this
connection or interface while on the network w/the domain.

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 68.240.98.163
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 68.240.98.163
DNS Servers . . . . . . . . . . . : 68.28.186.11
68.28.178.11
NetBIOS over Tcpip. . . . . . . . : Disabled

I'm confused....where's your Ethernet adapter's IP config ?




Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{266F235D-0EF4-424C-9484-241869BAB734}
Browsing is active on domain.
Master browser name is: LIFEBOOK

Hmm - well, unless this computer normally participates in another (home)
network, I'd probably stop & disable the computer browser service on it.

Master browser is running build 2600
1 backup servers retrieved from master LIFEBOOK
\\LIFEBOOK
There are 0 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{266F235D-0EF4-424C-9484-241869BAB734}
There are 1 domains in domain MSHOME on transport
\Device\NetBT_Tcpip_{266F235D-0EF4-424C-9484-241869BAB734}

Please correct me if I've assumed anything incorrectly...it's been known to
happen.



.

Relevant Pages

  • Re: Access denied to computer in network neighborhood
    ... but merely in a simple workgroup. ... Michael Giorgio - MS MVP wrote: ... >>access a particular computer in the network neighborhood. ... You might not have permissions to use this ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Workgroup Home Network Security
    ... on a home workgroup and both have XP Professional loaded. ... permissions and NTFS permissions. ... Network or another loose permission, but it won't work with my name. ... Please post any reply as a follow-up message in the news group ...
    (microsoft.public.windowsxp.network_web)
  • Re: Cant access shares in the workgroup (help needed)
    ... workgroup resources after restoring from previous night ... after plugging it in my home network again, ... >the article title or PSS number for more information. ... >Description of File Sharing and Permissions in Windows XP ...
    (microsoft.public.windowsxp.security_admin)
  • Re: problem sharing folders and files with Win2kPro
    ... are on your computer to share permissions. ... > network and connect to other Pc's on the network, ... > rest of the workgroup or workgroups that are on the LAN. ... > fix it i have been trying to fix it myself now for 3 days, ...
    (microsoft.public.win2000.security)
  • Re: Network Neighborhood
    ... > inability to browse by using Network Neighborhood in Windows 95 or Windows ... > communicated effectively with the other workgroup computers. ... > not have a common networking protocol, a common workgroup, and common user ... the computer that is running Windows ...
    (microsoft.public.win2000.networking)