Windows Sever 2003 domainUser is a domain administratorSuccessfully connects and saves files on XPWhen I connect to a server network share with Windows 7 I can open the file but I cannot save it. The errormessage: "You need permission to perform this action".No entries in the event log.Help!Thanks,Tom

I have a similarly problem. If I open a file from share width pspad last version and edit this, press save, i get an error message, BUT THE FILE SIZE IS SET TO THE NEW SIZE and the content is the old one. another thing is if I open a command promt with admin rights, I can't open the bound network share. If I type "net use", it shows the share is connectet. If I retype net use x: \\server\share its says ready and I can switch to x: . After a reboot I must do this every time!!! this is also a problem when I would update hardware drivers from this net drive

Where is the shared folder? On a domain member computer, a server computer, or a network device such as NAS? Also please check if you have correct permission on the specified folder. Arthur Xie - MSFT

In my case I found the problem: the server is Small Business Server 2003. SBS 2003 required this update (http://www.microsoft.com/downloads/details.aspx?FamilyID=9bf2f1e4-1b2c-471b-a284-e0c8c169fac3&displaylang=en) to support Vista/Windows 7.Thanks,Tom

In my case I found the problem: the server is Small Business Server 2003. SBS 2003 required this update (http://www.microsoft.com/downloads/details.aspx?FamilyID=9bf2f1e4-1b2c-471b-a284-e0c8c169fac3&displaylang=en) to support Vista/Windows 7.Thanks,Tom I seem to be having this same problem except with W2k3 server, not SMB Server 2k3, but I can't find an update for W2k3 without the SBS. XP has no problems, and my Windows 7 box doesn't have a problem mapping to Windows server 08 or windows xp, but will map to a w2k3 server but gives read-only permissions to that server. Any ideas? Thanks!

Solved. Ok, so it wasn't the same problem but it seemed to act the same. I realized that some W2k3 shares worked while others were only readonly. So investigating what's different exposed the fact that you can't just rely on the security permissions of files and folders when mapping with Windows 7, you have to also be sure to set the share permissions. Seems like XP didn't care about this and if the user accessing the resource had file or folder level permissions that was good enough. Now the share permissions is fully enforced as well.So if this snags anyone else up, go to the server where you created the share, open Windows explorer, navigate to the share, right click, click properties, choose Sharing tab, select share name from drop down, click permissions, make sure your desired users are in this list.

HI Arthur! I have the same problem here. New laptop with Win7 Pro, user logon is part of the domain, we have server 2003, we have network shared folder located on the server computer, the same logon name used on the old computer with full permission on that particular folder and no problem on the old laptop with WinXP. When we finished the initial setup of the new laptop, we added it to the domain using the same logon name used from the old laptop. We can see the shared network folder, we can see the files, but we cannot save on that network shared folder located on the server computer.