Willemoe’s Weblog

http://support.microsoft.com/kb/555632

Se artikel: http://www.computerhope.com/issues/ch000646.htm

Se artikel: http://support.microsoft.com/kb/258470/

Se artikel: http://support.microsoft.com/default.aspx?kbid=240145

Se artikel : http://support.microsoft.com/kb/147524/

I share
HOME and PRO all the time with no problem.  I set up an automatic routine on the HOME box so I don’t have to mess with things more than once.
   
Here’s what I do to share out an entire drive:
1. In PRO right click on drive go to properties and sharing tab.
2. I click ‘New Share‘ and name it CDrive.
3. I click ‘Permissions’ and give everyone full control.
4. After OK’ing back to the PC desktop I write down a username and password that can log into the PRO so I have that info handy.
5. I go to START–>RUN and type cmd.  Once a DOS box pops up I type ‘ipconfig’.
6. Write down the IP Address and close the DOS window.
7. Go to my HOME pc, goto START–>RUN and type cmd.  Once a DOS box popus up type ping and then the ip address you wrote down e.g. (ping 10.233.222.222).  Then hit enter.  If you get a reply proceed.  If not then you can’t talk to the machine until you can ping it.
8. On the HOME pc you’ll use the net use command to access the PRO Box automatically. Here is NET USE syntax:
net use DRIVE_LETTER: \\IP_ADDRESS\SHARE_NAME PASSWORD /USER:Computer_Name\USERNAME /PERSISTENT:NO

for example if my computer name is PROBOX and my username is John and my password is pass I would type into notepad
net use x: \\10.233.222.222\CDrive pass /user:PROBOX\John /Persistent:no
9. I then go to File Save As Connect.bat
10.  Then anytime you want to connect click Connect.bat and it will map an X Drive on your Home box to the CDrive share on the Pro Box.

Didn’t mean to write that much but it kept on going.  Guess I’m trying to keep from working.  Let me know if you have any questions.

At home we have a Windows 2003 Server running as a domain controller and file server. Whilst this does its job pretty nicely for Windows clients, I’ve never been able to connect to it successfully with my Mac running OS X 10.3 Panther. Browsing the network I have always been able to see the server, but any attempt to authenticate simply returned a error along the lines of “the original item cannot be found”. Frustrating.

In a nutshell, the cause of the problem is the default security policy on Windows 2003 Server being set to always encrypt network connections under all circumstances. Whilst this is fine for most clients (especially Windows clients, understandably), the version of SMB that Panther uses doesn’t support encrypted connections. Apparently this support exists in Samba 3, but not on the version OS X uses. The solution is to change the security policy to use encryption when it’s available and not otherwise. Here’s how.

From Administrative Tools, open Domain Controller Security Settings.
Go to Local Policies then Security Options.

Scroll down to find the entry Microsoft network server: Digitally sign communications (always). Set this to Disabled.

The only thing left to do is to reload the security policy, as changes don’t otherwise take effect for some time. Open up a command window and type:

gpupdate

This will buzz and whirr for a few moments before confirming that the policy has been reloaded. With a bit of luck you should now be able to mount a network share from the Windows 2003 Server on your Mac. As I say, I’ve been searching for this information periodically for more than six months, so if you find it helpful pass it on.

http://support.microsoft.com/default.aspx?scid=kb;en-us;305293&Product=winxp

http://www.terranovum.com/docs/energystar/EZ_GPO/doc.html