Realtek issues fixed by using jumbo frames settings

[Sam L.]

freenas error code 80004005 (I was unable to connect to the share) plus a couple other issues.
===============
Background : I run Win7 x64 Ultimate, private network, running my own NTP on my win7 machine because I don't want to put my nas on the internet and it never wants to stay in synch with my laptop.

Hardware for freenas is:
1 Gigabyte (GA-H87TN) (ultrathin miniITX)
1 Intel Core i5-4460 LGA 1150 CPU (BX80646I54460)
1 Plextor M6M 128GB mSATA SSD (PX-128M6M)
12 Samsung Spinpoint (ST2000LM003) (2TB 2.5inch HDDs)
1 Protronix 8-Port PCI Express SataIII controller
2x8GB Corsair Vengeance (CMSX16GX3M2B1600C9) DDR3L 12800 Laptop memory

(thats 24 TB NAS in a 1.3x15x11 inch form factor! and average power consumption of 30watts. Peak power is 67watts so far.)

The freenas is a stand alone pc with wired network card going via crossover cable into my second pc (my laptop). The link between the two is a private IP scheme without DHCP. The laptop has a separate wifi link to the internet and is not sharing it.
---------------
I ran through the video tutorial to build my nas and share. I used the online video that demos 'freenasiscool' for ver 9.3, ultimately setting up a 12 drive raidz, making a volume, making a dataset, making a share.

I was unable to connect to the nas via the setup cifs share, even when only setting force guest. Seaching online help for 3 days led to no progress. Finally I found someone who pointed out that you can force windows to select "alternate credentials" when using the map network drive wizard! I know how to setup user credentials in windows, and despite setting up in freenas that the user was a windows account, my win7 pc would always attempt to authenticate as a generic credential; see windows credential manager. I had setup and check this more than 50 times. Ironically, despite configuring and logging is as the same user over and over again I had to use the wizard where I could check the box that says "use alternate credentials" with my credentials input as "10.10.10.1\freenasiscool" then the password, then check the box to save it. Windows 7 would not accept manually putting in these credentials any other way.

Also I had to check the adapter settings, as it needed the "Client for Microsoft Networks" installed, as well as under IPv4 I had the NetBIOS "Enable NetBIOS over TCP/IP" checked. I disabled IPv6 all around to reduce any other issues that could arise.

I also had to go into my firewall (Symantec) and configure the rule "Allow UPnP Discovery from private IP addresses" I did this not so that it would work for default login now, but for future services that I wish to enable on the server.

Now I can finally get in, see my directory, make files, delete files, and modify them as well. Unfortunately I further have the issue that copying over a single 54MB file took 30+ minutes, as the transfer rate is right at 28KB/s.

To fix slow transfer to the nas I found how to add options to the network interface. Go to the Network -> Interfaces -> click on yours (mine was re0) in the options set "mtu 9000 up" which I also had to set on the other side of the network link at my laptop. After rebooting the NAS my upload speeds went from 30kbps to 122MB/s peaking out the gigabit LAN.

I hope that some of this helps another person out there.

PS: I posted this here because it directly relates (partially) to jgrecos comments on jumbo frames and their effect on the network throughput.

 

[Ericloewe]

freenas error code 80004005 (I was unable to connect to the share) plus a couple other issues.
===============
Background : I run Win7 x64 Ultimate, private network, running my own NTP on my win7 machine because I don't want to put my nas on the internet and it never wants to stay in synch with my laptop.

Hardware for freenas is:
1 Gigabyte (GA-H87TN) (ultrathin miniITX)
1 Intel Core i5-4460 LGA 1150 CPU (BX80646I54460)
1 Plextor M6M 128GB mSATA SSD (PX-128M6M)
12 Samsung Spinpoint (ST2000LM003) (2TB 2.5inch HDDs)
1 Protronix 8-Port PCI Express SataIII controller
2x8GB Corsair Vengeance (CMSX16GX3M2B1600C9) DDR3L 12800 Laptop memory

(thats 24 TB NAS in a 1.3x15x11 inch form factor! and average power consumption of 30watts. Peak power is 67watts so far.)

The freenas is a stand alone pc with wired network card going via crossover cable into my second pc (my laptop). The link between the two is a private IP scheme without DHCP. The laptop has a separate wifi link to the internet and is not sharing it.
---------------
I ran through the video tutorial to build my nas and share. I used the online video that demos 'freenasiscool' for ver 9.3, ultimately setting up a 12 drive raidz, making a volume, making a dataset, making a share.

I was unable to connect to the nas via the setup cifs share, even when only setting force guest. Seaching online help for 3 days led to no progress. Finally I found someone who pointed out that you can force windows to select "alternate credentials" when using the map network drive wizard! I know how to setup user credentials in windows, and despite setting up in freenas that the user was a windows account, my win7 pc would always attempt to authenticate as a generic credential; see windows credential manager. I had setup and check this more than 50 times. Ironically, despite configuring and logging is as the same user over and over again I had to use the wizard where I could check the box that says "use alternate credentials" with my credentials input as "10.10.10.1\freenasiscool" then the password, then check the box to save it. Windows 7 would not accept manually putting in these credentials any other way.

Also I had to check the adapter settings, as it needed the "Client for Microsoft Networks" installed, as well as under IPv4 I had the NetBIOS "Enable NetBIOS over TCP/IP" checked. I disabled IPv6 all around to reduce any other issues that could arise.

I also had to go into my firewall (Symantec) and configure the rule "Allow UPnP Discovery from private IP addresses" I did this not so that it would work for default login now, but for future services that I wish to enable on the server.

Now I can finally get in, see my directory, make files, delete files, and modify them as well. Unfortunately I further have the issue that copying over a single 54MB file took 30+ minutes, as the transfer rate is right at 28KB/s.

To fix slow transfer to the nas I found how to add options to the network interface. Go to the Network -> Interfaces -> click on yours (mine was re0) in the options set "mtu 9000 up" which I also had to set on the other side of the network link at my laptop. After rebooting the NAS my upload speeds went from 30kbps to 122MB/s peaking out the gigabit LAN.

I hope that some of this helps another person out there.

PS: I posted this here because it directly relates (partially) to jgrecos comments on jumbo frames and their effect on the network throughput.

I'm sorry, but who in their right mind would follow the advice of someone who can't even be bothered to get proper hardware and pretty much goes against common knowledge (use of RealCRAP NICs) and this very thread (Careless use of jumbo frames)? Not to mention that it's not related to FreeNAS.

 

[jgreco]

I've pruned this from the jumbo frames sticky since it has virtually nothing to do with jumbo.

As previously noted, Realtek chips suck, and what the poster has actually discovered is that there was either a configuration, driver, or hardware issue that was preventing the onboard Realtek from working correctly, or possibly the client-side had an issue. Twiddling jumbo on causes different things to be exercised, and the poster did was went from a broken/unworkable configuration to something that worked approximately correctly. Different bits of code are exercised for jumbo frames in many of the drivers, and there may be hardware implementation differences as well. We don't closely track the Realtek stuff here because it's been proven time and time again to be extremely problematic. The difference in performance that jumbo offers is only a few percent, and obviously the Realtek should have been operating at 900Mbps++ even at 1500 byte frames. That using jumbo fixed this is only an incidental issue; it might also have been fixed by inspecting the wire traffic to see if maybe the chip was failing to send 1500 byte traffic ("what it sounds like to me"), in which case setting the mtu to something just above 1500 might have worked, or maybe there was a duplex issue.

We don't really care for this selection of parts for the mainboard and CPU for a whole bunch of reasons. However, I think the use of 2.5" drives is interesting; I'll note that I'm doing something similar in the VM storage server I'm working on (including using the Samsung/Seagate Spinpoint part).

 

[marcevan]

Just chiming in here.

On my Win7 HTPC: Intel Ethernet from mobo at full gigabit
Gigabit Master Slave Mode: Auto
Jumbo Packet: Disabled
Large Send Offload (IPv4): Enabled

I typically get somewhat slow ~35Mbps on file transfers to the NAS downstairs.

I wire thru Fios Actiontec router to a downstairs switch which then wires to NAS and a Win8 PC.

NAS has Intel PCI-e board for networking.
Win8 has whatever is on the mobo and typically does ~~75Mbps transfers to the NAS.

So not sure if it's the Win7 settings (haven't played around with jumbo frames) or the Actiontec router but getting 1/2 the speed and starting to get playback stuttering and audio out of sync on >10GB movies streaming to it from NAS.

 

[Mlovelace]

I wire thru Fios Actiontec router

These routers typically have 10/100 network ports so if you are plugging directly into that router it might explain your poor speeds.

 

[jgreco]

These routers typically have 10/100 network ports so if you are plugging directly into that router it might explain your poor speeds.

The FiOS ones are more likely to be gigabit-capable, though that's no guarantee that they're capable of gigabit throughput.

If he's only getting 35Mbps to 75Mbps, there's obviously lots going on that is wrong, because the setup indicated in signature ought to be capable of far more than 1/20th of a gigabit. Jumbo obviously isn't going to fix that and is only going to increase the pain.