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: 2018-01-11

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

Experts Exchange Solution brought to you by

Enjoy your complimentary solution view.

Get every solution instantly with Premium. Start your 7-day free trial.

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

LVL 106

JohnBusiness Consultant (Owner)Commented: 2018-01-11

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.

LVL 47

Shaun VermaakTechnical Specialist/DeveloperCommented: 2018-01-11

Did you use Disk2VHD for a Domain Controller?

LVL 2

Kostas KostasIT AdministratorCommented: 2018-01-12

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

AgrippaSenior IT ConsultantAuthor Commented: 2018-01-12

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?

LVL 106

JohnBusiness Consultant (Owner)Commented: 2018-01-12

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.

AgrippaSenior IT ConsultantAuthor Commented: 2018-01-12

I need this drivers, then I think it might work: Intel 82371ABEB PCI to ISA bridge (ISA mode)

I cannot find this driver

LVL 106

JohnBusiness Consultant (Owner)Commented: 2018-01-12

A guest machine must use the driver supplied by Hyper-V (or if that will not work) then VMware.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial

AgrippaSenior IT ConsultantAuthor Commented: 2018-01-18

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.