Line One
asked on
HyperV - problem copying large files to virtualized SBS 2003/DC's
I have discovered a problem with an SBS2003 server running in a HyperV session. When I copy a large file (100mb+) to the virtual SBS2003 server it will time out and fail. All internal file copy operations work okay. It is like the Hyper-V virtual Nic is faulty. The system was using an internal NIC so I tried adding an Intel NIC and made it the NIC for the SBS 2003 virtual machine and left the original NIC for the host server. Same issue. When I copy a large test file (1gb VHD) to the SBS2003 drive(s) or domain controller I get a "Read-only" error message after 5-10 seconds and the copy aborts. Small files copy okay. No problem with virtualized 2003 member servers. I tried turning off large packets and also tried 100 megabit through flow control
System is running with one virtual processor.
My version of Hyper-V is 6.00.6001.1816
System is running with one virtual processor.
My version of Hyper-V is 6.00.6001.1816
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
YES TOE!!! I had this problem also. Disable this on the host NIC & your slowness should go away.
ASKER
I am hoping to get to this over the weekend.
Great! Let us know what happens.
ASKER
Ok. I tried all the remedies. Nothing worked. I changed the RAM and the problem seemed to get 'better' but not completely go away. The copying would go through but when I compared some large files - copied from/copied to - there were size differences/corruption. Unfortunately at this point I stopped being methodical - it was taking too long to do 'step-by-step' and I was under time pressure to get the system into production so I worked by 'feel/desperation'. I played with BIOS and changed hard drives, put back old RAM, etc. At the end of a lot of these shots in the dark the problem seems to have gone away - with the old RAM and the original settings minus any of the tweaks recommended here. So it's working but I can't say why. I guess that's better than not working and not being able to say why. Sorry I can't be more helpful.
ASKER