Guest Mike Bonvie Posted May 16, 2008 Posted May 16, 2008 Hello, This one is driving me completely insane. 1 domain\site I have a 2008 x64 SP1 server running as a Hyper-V host - the host also hosts all the user\corp data shares the 2 DCs are 2008 x64, no 2003 DCs Fresh install of XP SP3 on a physical machine (not a VM), fully updated - (this behavior also is replicated on a XP SP3 VM) heres the situation: from my vista sp1 client I can browse the root \\server & all shares \\server\shares whether logged in as a user, or a domain admin from the xp box i cannot do either above, even using \\ip-address\ - I get this error: "the network name is no longer available" i went as far to install wins in my environment, add the wins entry to all servers tcp\ip properties, added to DHCP scope, on all the 2008 servers: tcp\ip properties\ unticked ipv6, link-layer topology discovery mapper i/o driver, link-layer topology discovery responder file and printer sharing-enabled client for microsoft networks-enabled (in the properties\name service provider, none ("blank") was selected - set to "windows locator" applied, go back..it reverts to none again (none meaning "blank") the shares were created the old school way, new folder\share permissions(everyone-full)ntfs permissions-set correctly, no permissions altered on the root drive even stranger....from the xp boxes I can browse the DC (2008) shares ....sysvol... i can ping the server hosting the shares by name, what does it take to accomplish this? Is it even possible?
Recommended Posts