tsukraw
asked on
SBS2008 on VMware ESXi 4.1 SLOW SMB
I have a brand new Vmware setup with a SBS2008 server. It is on a HP DL360G6 server.
For some reason the transfer rate from the Server to the clients is horrible. Max speed i can get is around 100KB a sec. But loading from the client to the server i can get 2-6MB....
If i try FTP or any other protocal to transfer from the server it is fast it is only SMB that is slow. It is not just one machine it is on all the client computers (9 workstations) they are all running windows XP and joined to the domain.
The SBS2008 is the only VM on this server. We are using a single NIC in the server as there isnt much need to use the second one since there is limited use anyways.
The server has 8GB ram and 4x146GB SAS drives...
I found article http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006619
But that did not seem to have much effect.
For some reason the transfer rate from the Server to the clients is horrible. Max speed i can get is around 100KB a sec. But loading from the client to the server i can get 2-6MB....
If i try FTP or any other protocal to transfer from the server it is fast it is only SMB that is slow. It is not just one machine it is on all the client computers (9 workstations) they are all running windows XP and joined to the domain.
The SBS2008 is the only VM on this server. We are using a single NIC in the server as there isnt much need to use the second one since there is limited use anyways.
The server has 8GB ram and 4x146GB SAS drives...
I found article http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006619
But that did not seem to have much effect.
You mentioned this:
"The SBS2008 is the only VM on this server."
Are you saying then that this sbs2008 is a guest on your vmware host?
As bgoering also mentioned, please specify what VMware server version you are running, this will help us get to an accurate resolution.
"The SBS2008 is the only VM on this server."
Are you saying then that this sbs2008 is a guest on your vmware host?
As bgoering also mentioned, please specify what VMware server version you are running, this will help us get to an accurate resolution.
ASKER
Sorry about that.
It is ESXi 4.1
SBS2008 is the only VM running on the server.
It is ESXi 4.1
SBS2008 is the only VM running on the server.
In that case just make sure of steps 1 and 2 I posted above, leave tcp offload settings alone on ESXi
ASKER
I had already installed the VMware tools should i reinstall them or just try switching the NIC to vmxnet3 it is on E1000 right now.
ASKER
Ok i was looking around and seen someone talking about the NIC in a VM. They have a screen shot of the drivers and it says VMware for the NIC drive.
I looked at my VM and it says "Intel Pro/1000 MT Network Connection" Does that mean it doesnt have the proper driver installed for it? Or is that what a E1000 is listed as?
I looked at my VM and it says "Intel Pro/1000 MT Network Connection" Does that mean it doesnt have the proper driver installed for it? Or is that what a E1000 is listed as?
It means that it the E1000 driver. I would uninstall the nic and install a VMXNET3 driver to baseline.
You should also upgrade G6 bios, there were a few issues with vmware and the servers with older bios sets.
What speed do you see the nic connected on the vswitch? Is the client on the same switch or a different one and what is the line speed.
You should also upgrade G6 bios, there were a few issues with vmware and the servers with older bios sets.
What speed do you see the nic connected on the vswitch? Is the client on the same switch or a different one and what is the line speed.
ASKER
The switches are showing 1Gb connections to the physical switch and on the vswitch.
With the client you are referring to the physical switch? If so yes the client is on the same switch and is connected at 1Gb as well.
With the client you are referring to the physical switch? If so yes the client is on the same switch and is connected at 1Gb as well.
Yes, switch your NIC type to vmxnet3, if tools are already installed it should configure the proper driver. If you have custom tcp/ip settings you will have to enter them again, if you are using dhcp it will just pick up a new ip address.
Good Luck
Good Luck
ASKER
I am switching it right now. This is the DHCP server and all so i will assign it static info again.
ASKER
Ok here is a update.
On the SBS2008 in removed the E1000 and installed the vmxnet3. Got the same results around 100kb/s to workstation.
So i just loaded up a Server2003 standard on the same ESXi server to test with.
SBS2008 to Server2003 transfer is fast like it should be.
Server2003 to workstation transfer is fast like it should be.
So there is some issue with the SBS2008 and VMware i am guessing correct?
Any other ideas on what to try? I did also reload vmware tools just to see if that would help.
On the SBS2008 in removed the E1000 and installed the vmxnet3. Got the same results around 100kb/s to workstation.
So i just loaded up a Server2003 standard on the same ESXi server to test with.
SBS2008 to Server2003 transfer is fast like it should be.
Server2003 to workstation transfer is fast like it should be.
So there is some issue with the SBS2008 and VMware i am guessing correct?
Any other ideas on what to try? I did also reload vmware tools just to see if that would help.
I am thinking it may be a microsoft issue. Try this on your 2008 server:
1. Open your local area connection properties.
2. Click Internet Protocol (TCP/IP), and then click Properties.
3. Click Advanced.
4. Click the WINS tab, and then click Disable NetBIOS over TCP/IP.
See how that goes - Windows 2000 and up prefer using SMP for file share, sometimes NBT just gets in the way.
1. Open your local area connection properties.
2. Click Internet Protocol (TCP/IP), and then click Properties.
3. Click Advanced.
4. Click the WINS tab, and then click Disable NetBIOS over TCP/IP.
See how that goes - Windows 2000 and up prefer using SMP for file share, sometimes NBT just gets in the way.
Take a look at the bindings on the nic. I have done a few SBS servers and haven't had issues. Try disabling firewall, disabling IPV6,etc..
ASKER
Can u disable IPV6 on SBS i thought i read somewhere that sharepoint or exchange or some service of SBS2008 used IPV6?
If not what is the best way to disable it?
If not what is the best way to disable it?
It is my understanding to leave ipv6 enabled for windows 2008 and windows 7 - something breaks if you don't but I don't recall right off what that something is.
oh, and i meant SMB (Server Message Block), not SMP!
ASKER
Ok i am testing the NetBIOS idea right now. If that does not work i will try disabling the firewall on the server.
ALSO i just tested this.
I physical 2003 server connected to the same physical switch at 1Gb/s had FAST transfer rates.....
So it is like there is a issue between XP and the server.
I have tried moving a workstation by the server and hooking a cable to the switch to rule out bad wiring in the walls...same slow results on that.
ALSO i just tested this.
I physical 2003 server connected to the same physical switch at 1Gb/s had FAST transfer rates.....
So it is like there is a issue between XP and the server.
I have tried moving a workstation by the server and hooking a cable to the switch to rule out bad wiring in the walls...same slow results on that.
Your original question said FTP was fine so I should have been focused on the SMB part of the thing from the start
ASKER
NetBIOS - same issue
Disabling firewall - same issue
If i run a FTP client on the workstaion and connect to the server (using filezilla ftp server and client) i am able to transfer fast like it is Gb connected....
Also i said above. If i can move files from the VM 2003 to the workstation with SMB just fine no issues.
Disabling firewall - same issue
If i run a FTP client on the workstaion and connect to the server (using filezilla ftp server and client) i am able to transfer fast like it is Gb connected....
Also i said above. If i can move files from the VM 2003 to the workstation with SMB just fine no issues.
Hmmm, do you have a Vista or Windows 7 client to test from? Reason I ask is my research is showing that there is a new SMB v2 protocol. See http://www.petri.co.il/how-to-disable-smb-2-on-windows-vista-or-server-2008.htm. You might consider disabling it on your 2008 long enough to test your xp/2003 client and see if we are barking up the right tree this time.
ASKER
Windows 7 - Fast
The windows 7 is not joined to the domain it is just a laptop but it is able to transfer fast.
Do you think it is a SMB v2 issue?
I was actually looking at that exact same artical earlier and was wondering that same thing.
I have multiple SBS2008 on ESXi and never had this issue before...Should i try disabling SMB2?
The windows 7 is not joined to the domain it is just a laptop but it is able to transfer fast.
Do you think it is a SMB v2 issue?
I was actually looking at that exact same artical earlier and was wondering that same thing.
I have multiple SBS2008 on ESXi and never had this issue before...Should i try disabling SMB2?
Found another EE thread (https://www.experts-exchange.com/questions/24123181/Slow-speeds-accessing-files-from-Windows-Server-2008-Standard.html) recommends turning off tcp/udp checksum offload to fix the problem. But just try one thing at a time, and put it back the way it was if it didn't work!
yeah - I would try it to see if it helps XP - it very well could be the smb v2 issue, but I don't understand how it would fail to negotiate smv v1 with an xp client
ASKER
checksum offload made it even slower.....
When looking at the SMB v2 artical i see
sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc config mrxsmb20 start= disabled
sc config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/n si
sc config mrxsmb20 start= auto
Do i do either of those or do i just do the registry key one?
When looking at the SMB v2 artical i see
sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc config mrxsmb20 start= disabled
sc config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/n
sc config mrxsmb20 start= auto
Do i do either of those or do i just do the registry key one?
The way I read it just do the registry key on the server then reboot
Based on another article - from XP is writing slow and reading fast? If so look at http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/46898c7f-92e0-4c99-98d2-18a7458a7d2d and http://support.microsoft.com/kb/951037 about NetDMA - I still haven't run out of things to try!
ASKER
Haha alright i will give that a try if the disable SMB2 doesnt work. I think i am going to pass up his 30 reboots in 3 weeks....to 30 reboots in a day.
ASKER
O gzz this is ridiculous haha....
Disable SMB2 - NO fix
Disable NetDMA - NO fix
I tested transfering SBS2008 to windows XP works fast. Like i from the SBS2008 i network browsed to the XP and i could transfer to it fine.....
But on the XP machine browsing to the SBS2008 it is so ungodly slow.
What other ideas do you have short of calling Microsoft...
Disable SMB2 - NO fix
Disable NetDMA - NO fix
I tested transfering SBS2008 to windows XP works fast. Like i from the SBS2008 i network browsed to the XP and i could transfer to it fine.....
But on the XP machine browsing to the SBS2008 it is so ungodly slow.
What other ideas do you have short of calling Microsoft...
Well, all I have left is upgrade XP client to Windows 7
Just kidding, one more thing for tonight (because I am off to bed soon) is try enabling or disabling tcp auto tuning. Saw a couple references where that caused problems. This article (http://www.mydigitallife.info/2007/03/22/disable-tcp-auto-tuning-to-solve-slow-network-cannot-load-web-page-or-download-email-problems-in-vista/) tells how. I would expect that to be an issue over WAN connection though - not LAN, but anything is worth a try at this point.
Double check for hardware mismatch, especially duplex - again I really doubt it or Windows 7 and FTP would likely be slow.
There are other offload things to try to disable, I would go through all of the things in advanced properties that refer to offload and turn them off, then if you see any improvement start turning them back on one at a time. Truth is it should perform well even with all turned off.
Lastly, you might want to add the question to OS group for Windows 2008i and/or Microsoft networking, might get the attention of some experts there.
I will check on the status in morning - Good Luck
Just kidding, one more thing for tonight (because I am off to bed soon) is try enabling or disabling tcp auto tuning. Saw a couple references where that caused problems. This article (http://www.mydigitallife.info/2007/03/22/disable-tcp-auto-tuning-to-solve-slow-network-cannot-load-web-page-or-download-email-problems-in-vista/) tells how. I would expect that to be an issue over WAN connection though - not LAN, but anything is worth a try at this point.
Double check for hardware mismatch, especially duplex - again I really doubt it or Windows 7 and FTP would likely be slow.
There are other offload things to try to disable, I would go through all of the things in advanced properties that refer to offload and turn them off, then if you see any improvement start turning them back on one at a time. Truth is it should perform well even with all turned off.
Lastly, you might want to add the question to OS group for Windows 2008i and/or Microsoft networking, might get the attention of some experts there.
I will check on the status in morning - Good Luck
ASKER
No luck with that either....
What end do you think the issue is at? Should i be be looking at turning offloading off on the XP side of it or do you think the issue is on the SBS side of the fence?
By the looks of this it appears that i am going to need to call microsoft which i was hoping not to have to do...
What end do you think the issue is at? Should i be be looking at turning offloading off on the XP side of it or do you think the issue is on the SBS side of the fence?
By the looks of this it appears that i am going to need to call microsoft which i was hoping not to have to do...
How about connecting the xp system to the ESX host via crossover cable during a maintenance period to take the switches out of the equation
ASKER
Hmm could give that a try. I actually tested it with 3 different model switches all had the same result but i did not try it without the switch entirely.
tsukraw I haven't really been able to find any more specific items to try. I am assuming you have tried disabling all of tcp/udp/segment offloading options in your nic properties?
ASKER
Ok update. I have tried a crossover cable directly to the server to rule out the switch, the same speed issue existed. I tried moving the SBS2008 vm its own NIC same issue.
I have been on the phone with Microsoft for the last 3+ hours and am on hold right now. They cannot seem to find anything wrong with the server besides believing it could be a VMware issue.
I have been on the phone with Microsoft for the last 3+ hours and am on hold right now. They cannot seem to find anything wrong with the server besides believing it could be a VMware issue.
ASKER
Well microsoft did not seem to have any answers to the issue. I have a case open with VMware now and they have not called me back.
One thing that i did test with microsoft which i found interesting. I setup a windowsXP VM on the same vswitch as the SBS2008 server. Transfer rates betwen the 2 were GOOD. So that would point to a vmware issue wouldnt it?
One thing that i did test with microsoft which i found interesting. I setup a windowsXP VM on the same vswitch as the SBS2008 server. Transfer rates betwen the 2 were GOOD. So that would point to a vmware issue wouldnt it?
Not really. If you have a vswitch you're not going over the wire, all the traffic remains internal to the vswitch.
Try this..virtualize the XP machine you're having an issue with.
Try this..virtualize the XP machine you're having an issue with.
ASKER
Ok i am converting it now. Transfer with the converter is running at 4.3MB/s. So from that we know it is not a switch of wiring issue. No where near the KB speeds in windows.
ASKER
Ok i have spent hours on the phone with VMware and Microsoft and no one can seem to find the cause for this issue.
Can anyone out there tell these things?
1) Does anyone have a SBS2008 on a ESXI 4.1 If so what are you getting for a transfer speed to a client computer with a 10/100NIC?
2) Does anyone have a SBS2008 on ESXi 4.0. If so what are you getting for a transfer rate to 10/100?
3) Does anyone have a SBS2008 without a hypervisor? If so what is the transfer rate to a 10/100 client?
4) Does anyone have a Server 2008 on ESXI 4.0/4.1 If so what do you get for speed.
I am having trouble finding good answers to these questions internally at my company so i am hoping someone might be able to answer a couple of them!
Can anyone out there tell these things?
1) Does anyone have a SBS2008 on a ESXI 4.1 If so what are you getting for a transfer speed to a client computer with a 10/100NIC?
2) Does anyone have a SBS2008 on ESXi 4.0. If so what are you getting for a transfer rate to 10/100?
3) Does anyone have a SBS2008 without a hypervisor? If so what is the transfer rate to a 10/100 client?
4) Does anyone have a Server 2008 on ESXI 4.0/4.1 If so what do you get for speed.
I am having trouble finding good answers to these questions internally at my company so i am hoping someone might be able to answer a couple of them!
ASKER
UPDATE!
Figured out something here!!!
If i put the client machine on Half Duplex the transfer rate is 7MB/s If it is on Full Duplex it is slow.
I have tried this with a cross over cable from the server to the workstation as well. Same result so that should rule out the switch as being the cause. Any idea why this would be? I know it is a semi simple fix go around to all the client machines and set them to half duplex but there has to be a reason this would happen?
Figured out something here!!!
If i put the client machine on Half Duplex the transfer rate is 7MB/s If it is on Full Duplex it is slow.
I have tried this with a cross over cable from the server to the workstation as well. Same result so that should rule out the switch as being the cause. Any idea why this would be? I know it is a semi simple fix go around to all the client machines and set them to half duplex but there has to be a reason this would happen?
Most of the time the nic on the workstation or the switch and nic autodetect aren't synching properly. Try to setup 100mb/full on both the switch and the workstation. You could always try to add a spare nic into the workstation as baseline.
Is the win xp, server or switch on auto negotiate? I think you said you are using gig ethernet right? Set them both the same, auto/auto.
It used to be that you'd have one side set to a manual or static speed.duplex setting but now with gig, the standard actualy states that both ends are to be set to auto, and manual settings are only there to be compatible with earlier gig equipment that do not have auto negotiate settings.
Cheers,
Steve
It used to be that you'd have one side set to a manual or static speed.duplex setting but now with gig, the standard actualy states that both ends are to be set to auto, and manual settings are only there to be compatible with earlier gig equipment that do not have auto negotiate settings.
Cheers,
Steve
ASKER
Server is on Auto. It is going to 1000 FULL
Switch is set to auto on all ports
Windows XP is set to auto. It has a 10/100NIC and is getting 100FULL
When i did a cross over cable it went to 100FULL.
What would be the best way to do this. I cant set it on the switch because otherwise it would go to 100HALF even when there was a Gbit connected. There must be some reason why 100FULL isnt working isnt there?
Switch is set to auto on all ports
Windows XP is set to auto. It has a 10/100NIC and is getting 100FULL
When i did a cross over cable it went to 100FULL.
What would be the best way to do this. I cant set it on the switch because otherwise it would go to 100HALF even when there was a Gbit connected. There must be some reason why 100FULL isnt working isnt there?
Gig auto to 100 anything will most likely fail negotiation to half duplex (even if it doesnt show this). In this config you must set the switch port the same speed.duplex as the client pc (100/full)
ASKER
So u are thinking if i go into the switch and set it to 100/FULL the clients would work on 100/FULL also? That wouldnt explain why i had the same issue with a crossover cable though?
yup, i've seen it before, client and switch at 100/full and you'll get full, as soon as you change the other end to 1000 auto it will fail negotiation. not all switches or nics do this, but sometimes they just cant negotiate correctly and this method is your only option
give it a try, let us know.
cheers,
steve
give it a try, let us know.
cheers,
steve
Or for $10 get a GB nic for the workstation.
cheaper then a call to M$
ASKER
Haha i already have a case with Microsoft and Vmware...So $$ already spend.
I will look into the Switch and see if i can see anything in there.
I have another server in my test lab with ESXI 4.1 and SBS2008. It is a HP ML150G6. I got the same results. In my test setup i have a simple un-managed GB switch. I never noticed this in my test setup since everything is GB. But if i set a computer to 10/100FULL in the test lab it get the same slow speed 100/HALF i get fast speed. Say in that setup i have a unmannaged switch that i am not able to change the duplex on. There has to be something else wrong or a better solution then going to each workstation and either installing a GB nic or changing the Duplex manually...
I will look into the Switch and see if i can see anything in there.
I have another server in my test lab with ESXI 4.1 and SBS2008. It is a HP ML150G6. I got the same results. In my test setup i have a simple un-managed GB switch. I never noticed this in my test setup since everything is GB. But if i set a computer to 10/100FULL in the test lab it get the same slow speed 100/HALF i get fast speed. Say in that setup i have a unmannaged switch that i am not able to change the duplex on. There has to be something else wrong or a better solution then going to each workstation and either installing a GB nic or changing the Duplex manually...
ASKER
I am not sure if i mentioned this before. I loaded a 2003 standard server on the same ESXi host. The 2003 standard did NOT have a transfer issue with the windows XP machine. It is only the SBS 2008 that has the speed issue.
It's usually a nic/nic driver/switch combo. Doesn't happen all the time just makes you pull your hair out when it does. That's why it's good to start at Layer 1 and work your way up
See if you can disable IPV6.
ASKER
SBS2008 requires IPv6 i believe. I have read that somewhere that in SBS you should NOT disable that?
nope, i dont think so, it's likely the workstation card that's not compatible with the gig auto negotiate, not the gig side. you may find some workstations dont have this issue if they have different hardware in them (nic). unfortunately the only option is changing the gig auto or the workstation nic as mentioned above, sorry.
steve
steve
nope, i dont think so, it's likely the workstation card that's not compatible with the gig auto negotiate, not the gig side. you may find some workstations dont have this issue if they have different hardware in them (nic). unfortunately the only option is changing the gig auto or the workstation nic as mentioned above, sorry.
steve
steve
SBS2008 defaults with IPv6 enabled, however if you have to disable IPv6, make sure you follow the correct way of doing it:
Issues After Disabling IPv6 on Your NIC on SBS 2008
http://blogs.technet.com/b/sbs/archive/2008/10/24/issues-after-disabling-ipv6-on-your-nic-on-sbs-2008.aspx
Issues After Disabling IPv6 on Your NIC on SBS 2008
http://blogs.technet.com/b/sbs/archive/2008/10/24/issues-after-disabling-ipv6-on-your-nic-on-sbs-2008.aspx
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.
ASKER
Ended up replacing all the nics with Gbit nics. This didnt give us a solution to the real problem but was a cheap fix.
Things to try one at a time (in order) if you haven't already:
1. Install VMware tools in your guest
2. Change virtual NIC type to vmxnet3
3. On host, disable all TCP/IP offload settings in host machine's advanced NIC configuration
I have seen any or all of these improve performance in VMware Server 2, if you are using another product such as ESX or Workstation give us details
Good Luck