Do homegroups basically suck?

[Shyatic]

So I run a homegroup in my gigabit ethernet connected network, and it's just abysmally bad. Am I alone here? I constantly lose connection to shared folders, file copies are slow, etc. But it's convenient for the purposes of my house, and sharing things with my wife and kids.

 

I tested my network connection between my upstairs PC and server using iPerf (look it up, great tool):

------------------------------------------------------------

Client connecting to 192.168.1.115, TCP port 5001

TCP window size: 63.0 KByte (default)

------------------------------------------------------------

[  3] local 192.168.1.104 port 53925 connected with 192.168.1.115 port 5001

[ ID] Interval       Transfer     Bandwidth

[  3]  0.0-10.0 sec   822 MBytes   690 Mbits/sec

 

So I'm basically where I expect to be -- maybe a little slower than Gig-E but very acceptable. I don't NEARLY get this tranfer rate on file copies though; it's far slower.

 

Any tips or advice? Appreciate the help!

[JustGeorge]

I have issues losing connectivity with HomeGroup shares on my wireless network all the time. Seems like the best option is to go with the standard user account method of sharing files. I've read that HomeGroup relies on IPV6. Is your hardware fully compliant?

[+BudMan MVC]

While homegroup uses ipv6 to talk to each other the actual file transfer is not over ipv6.

 

Yeah homegroups suck, I agree with you.. But the copy shouldn't be slow.. While I could understand problems with access to shares, etc..  Once a file copy is started, its just a normal smb copy..  If that is slow you got something else going on causing the problem and not homegroups.

 

I would do a copy with robocopy from a share.. Your speed with iperf is fine..

 

Lets see a test with robocopy.. -- here is example from old test, in the middle of large file transfer currently or I would do current test.. But see getting over 100MBps -- what speed are you getting?