Cannot access shares in a virtualized system / Windows 2003 in Hyper-V

Hi everyone,

I have virtualized a Windows 2003 server into an Hyper-V environment with Disk2VHD. In the physical server I am able to do this:
\\servername\netlogon
I am able to see the content of netlogon.

When I do that in the virtual system (exact 100% the same Windows / setting / etc. offcourse) I get:
\\servername\netlogon is not accessible. You might not have the right permissions for this network location. Contact system administrator.

I do not get this permissions error since I cloned the physical to virtual, so everything should be exactly the same.

Anyone?
AgrippaSenior IT ConsultantAsked:
Who is Participating?
 
JohnConnect With a Mentor Business Consultant (Owner)Commented:
A guest machine must use the driver supplied by Hyper-V (or if that will not work) then VMware.
0
 
JohnBusiness Consultant (Owner)Commented:
Can you check that your Hyper-V networking is set to Bridged Mode. It needs to be for this.

Try using IP address for Server Name.
1
 
Shaun VermaakConnect With a Mentor Technical Specialist/DeveloperCommented:
Did you use Disk2VHD for a Domain Controller?
1
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Kostas KostasConnect With a Mentor IT AdministratorCommented:
Hi,

For domain controllers the recommend approach from Microsoft is the following

create a new Server and add  as DC.
Wait to replicate and check for errors
After verify that replication is ok degrade the old one and keep the new DC.

In any case you can check the following in your HYPERV

If network adapter of VM connected in appropriate Virtual Switch of HYPERV
If firewall is enable
If can ping the VM from other PC in same network
1
 
AgrippaSenior IT ConsultantAuthor Commented:
I did nog do anything with the network adapter since I need no network connection at all for my purpose. I need to be able to start a program on that server locally, that is all. I do need to be able to access a share locally though. My network adapter is not installed. The driver does work in the physical environment, but after virtualizing the driver is gone in the virtual environment.

Just reinstall the driver?
0
 
JohnBusiness Consultant (Owner)Commented:
Did you check that the guest network is in Bridged mode?

The network driver will be supplied by Hyper-V.  I am not sure Hyper-V supports Server 2003 (Microsoft does not).

You may need to consider a VMware platform.
0
 
AgrippaSenior IT ConsultantAuthor Commented:
I need this drivers, then I think it might work: Intel 82371ABEB PCI to ISA bridge (ISA mode)

I cannot find this driver
0
 
AgrippaSenior IT ConsultantAuthor Commented:
Hi John,

is there a way to create a fake network, I mean: install a driver for a card which does not exist. It seems I am not able to install the driver it needs.
0
 
JohnBusiness Consultant (Owner)Commented:
I do not think so. If you really need Server 2003, perhaps try using VMware as it still supports Server 2003 so far as I know
1
 
AgrippaSenior IT ConsultantAuthor Commented:
Ok thank you all!
0
 
JohnBusiness Consultant (Owner)Commented:
You are very welcome.  Good luck and please try VMware to fix your issue.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.