[adajun10]

hi,
i have a vm17 and a vm20 that connect just fine to a windows 2003 share. I have to retire that server since it's old, so I built a new 2008 R2 server. Neither vm can connect to the share on the new server. I suspect it's a dos to 2008 R2 thing. Has anyone else run into this problem? I found some stuff on the web that said I had to go into group policy on the 2008 R2 server and do the following.
Modify following Group Policy:
1) Start → Administrative Tools → Group Policy Management
2) Forest:<DomainName> → Domains → <DomainName> → (Right-Click) Default Domain Policy (Click Edit)
3) Computer Configuration → Policies → Windows Settings→ Security Settings → Local Policies → Security Options
4) Microsoft Network Server: Digitally sign communications (always): Disabled
5) From a DOS prompt: gpupdate /force

I did everything except step 2. step 2 is asking to set a policy for the whole company which my IT guys balked at. I just got into group policy on the server itself, not at the domain level.

anyone else run into this?

adam

here's a link to where I found the dos to 2008 R2 info

DOS network connectivity to Server 2008 R2 share

[ZZZZ]

I wish I could help but I haven't run into the problem (yet).

I have a client who put 2 NIC cards in a PC, one for the machines, the other for the office network.
Maybe this might work for you.

[Kenny Duval]

The domain policies will always override the local security policy on a domain joined machine. Talk to IT and get them to create a new OU nd policy for those machines that need access to the share.