asked on 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?
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?
VirtualizationWindows OSWindows Server 2003Hyper-V
Last Comment
John
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
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?
Just reinstall the driver?
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.
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.
ASKER
I need this drivers, then I think it might work: Intel 82371ABEB PCI to ISA bridge (ISA mode)
I cannot find this driver
I cannot find this driver
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
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.
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.
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
ASKER
Ok thank you all!
You are very welcome. Good luck and please try VMware to fix your issue.
Try using IP address for Server Name.