• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 921
  • Last Modified:

Windows 2003 and XP cannot access Windows 2008 share

Hi I've got a very strange issue, I have one windows 2008 machine running MS CRM and Dynamic GP. we have some shared folders on the server. The Folders can be seen and accessed by using the \\computername from all the windows clients including Windows 2003, XP, Vista and 2008 everytime it's rebooted. However, after a few hours or few days, all the windows 2003 and XP machines cannot access either \\computername or \\IPaddress and get the error saying cannot find the network path. but all the Windows 2008 and Vista machines can still access to all the shares by either \\computername or \\IPaddress.

And everytime when this happened, we tried to restart the "Server" service but it could not be restart and just stopped on the status "stopping".

The only thing we can do is to reboot the server and then the share would be accessable for the XP and 2003 machines for a few days but it'll stop again anyway.

Has anyone seen this issue and got any solution?
0
jsheppherd
Asked:
jsheppherd
1 Solution
 
arnoldCommented:
See whether you have IPv6 on the server and uncheck it from the network connection to see if it helps.  Also check the event logs application/system on the server and workstation for errors MRSMBx.
0
 
jsheppherdAuthor Commented:
Hi Arnold,

Thanks for replying. I've got the IPV6 on the other 2008 servers as well but they never give me the issue, anyway I'll turn IPv6 off and see how I go.

I searched the logs but there's nothing for errors MRSMBx....
0
 
vguzmanIT ManagerCommented:
Which network card are you using ?  Does it has the latest drivers ?
Also check the "power management" settings in your network card...
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
nicolausjCommented:
Hi,

What kind of server is it?
0
 
jsheppherdAuthor Commented:
Hi This is a Windows 2008 32 bit Enterprise. it has two Broadcon 1Gb nic and they are teamed as one, it has the latest drivers and in the power management the option of "allow computer to turn it off to save power" is not checked.

I don't really think it has anything to do with the network cards as all the xp, 2003, vista and 2008 machine can ping it and open the webpage(there's an IIS set up on the server), only problem is XP and 2003 machines cannot see the shares in a few days after rebooting
0
 
vguzmanIT ManagerCommented:
Are all the computers (XP, 2003, 2008) in the same domain ?  IF not, do you have trust relationaships ?
0
 
jsheppherdAuthor Commented:
Hi Vquzman,

yes all the machines are in the same domain
0
 
vguzmanIT ManagerCommented:
Can you try a workaround and setup a login script to map the network drives ?  maybe that way it will keep them connected...
0
 
jsheppherdAuthor Commented:
Hi Vquzman,

when it stopped serving the 2003 anf XP machines, mapping script stopped working as well.

I think I know the problem now, it was SMB 2.0 which is used in 2008 and Vista, but I cannot find any solution yet
0
 
vguzmanIT ManagerCommented:
Can you try

net use \\remote\sharefolder password /u:domain\username /persistent:yes

see if it stays connected, if it does add this as a login script, it could be done via GPO or via Active Directory.

http://www.petri.co.il/setting-up-logon-script-through-gpo-windows-server-2008.htm

or

http://www.petri.co.il/setting-up-logon-script-through-active-directory-users-computers-windows-server-2008.htm
0
 
vguzmanIT ManagerCommented:
0
 
jsheppherdAuthor Commented:
Hi Vquzman,

I can map a network drive or connect to it on XP and 2003 machines only a few hours or days after rebooting, the connection will be lost anyway. It has nothing to do with GPO as GPO only force you to run the script and there's nothing different running script or use the CMD on a local machine as administrator.

As far as I know, this issue is due to the SMB 2.0 newly imported to Vista and 2008. SMB2.0 use SMB2.0 to talk to vista or 2008 machines and use SMB 1.0 to talk to XP, 2003 and linux. when the 2008/vista machine decied to deny the service for a type of the client, it stopped serving all the SMB1.0 client.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now