February 10, 201313 yr This problem occurs totally random. When I want to enter one of my shares of my unraid machine from my windows computer, the following error pops up Basically it's saying something about a network error and that it's not able to access the share. What I do then, is start putty, connect to my unraid machine, exit putty again and then I'm able to access my shares without a problem. At least for a while. The error will occur again after a while and can be fixed the same way as before. So yea, would be cool if someone has a solution for this ...running unRAID 5.0-rc5 btw
February 12, 201313 yr Set your unRAID server to be your network's Master Browser. Apparently you might have some other machine on your LAN performing that task, and when it is off-line, the \\TOWER name cannot be resolved. Fined the setting under Settings->SMB Set "Local Master" to Yes. Joe L.
February 13, 201313 yr Author Hm besides from my Windows Computer and my HTPC, there are no other machines in the LAN my unRAID machine is in. But I'll try that as soon as I get home from work and will report back. Thanks in advance, Joe! €dit: So I'm finally home and I checked this setting and it was already set to "Yes". Got another idea?
February 13, 201313 yr Author ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000033 (51) Link detected: yes ifconfig eth0 Link encap:Ethernet HWaddr 00:25:22:8d:be:e4 inet addr:192.168.2.103 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1194533590 errors:0 dropped:16 overruns:0 frame:0 TX packets:1523385874 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3453118766 (3.2 GiB) TX bytes:4182089131 (3.8 GiB) Interrupt:41 Base address:0x4000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:791 errors:0 dropped:0 overruns:0 frame:0 TX packets:791 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:83136 (81.1 KiB) TX bytes:83136 (81.1 KiB)
February 14, 201313 yr Author That makes no real sense since I have no problems to connect to the machine via Putty at any times (like I stated in my first post)
February 14, 201313 yr He's not saying you cannot connect. You obviously have a good connection with successful networking over 99.9% of the time. But in your first post you mention very random network errors, and the ifconfig shows 16 drops (should be 0), so although the networking is good, it's not perfect. Perhaps a different cable or port will improve that. Or making sure a power cable is not running too close to the network cable. These suggestions may not have anything to do with your real issue, but we're just trying to help, with ideas that sometimes prove to be helpful in situations like yours.
Archived
This topic is now archived and is closed to further replies.