June 24, 20179 yr So I'm trying to get \\TOWER to pop up for a day or two now with no luck. trying to use the IP (\\192.168.x.x) has no desirable outcome either. I have edited the registry, enabled and disabled client for windows, turned all smb enabled devices and set unRaid as the smb master browser (HOWEVER despite this, other pc's claim to be master, I'm assuming because of the fact that \\Tower is not visible). I have also edited the host file with no success. I can access unRaid in the browser with the IP and http://Tower. Another thing, I was getting errors ranging from (0x80070035), (0x80004005) and (System Error. Code 64). I am currently stuck on issue (0x80004005) and can't find out how I'm going to replicate the other errors. Finally, I've reinstalled unRaid (copying over plugins and that is all, maybe this is where my issues lay (with no success). Here's a list of plugins I've used: nerdtools (with iftop and lftp) dynamix local master (to try and work out what's wrong) proftpd (no longer installed) If anyone can help me that would be fantastic! EDIT: added tower diagnostics tower-diagnostics-20170623-2301.zip tower-diagnostics-20170623-2301.zip Edited June 24, 20179 yr by Firelfy
June 24, 20179 yr Community Expert First read this post: If you are still having problems after this: First make sure that your unRAID server is the Local Master. Second, try booting in the "OS Safe Mode (no plugins, no GUI)" option on the unRAID boot menu. Of course the Local Master plugin would be working... Third, there is a program that will run on Windows computers that will tell you what computer that computer is using as the Local Master. You can find it here: https://scottiestech.info/2009/02/14/how-to-determine-the-master-browser-in-a-windows-workgroup/ (All of the usual warnings about downloading stuff from the Internet apply. I have used this program in the past and not had any problems.)
June 24, 20179 yr Community Expert Was looking through your diagnostics and found this for eth1: Settings for eth1: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Speed: Unknown! Duplex: Unknown! (255) Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: off (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) drv probe link Link detected: no Apparently, it is not detecting a physical connection to your network switch/router. (You see to be trying to use by the entries in the network.cfg.) Check to see that you have good connection, switch ports on the switch and replace the cable if necessary.
June 24, 20179 yr Author I did all the tests and set unraid to master browser with no success. What's weird about unraid not detecting the physical connection is I could still access the web interface... strange. I've since followed this: From another thread which has solved my problems. I'm thinking a rogue plugin (or something outdated) caused this issue or I did something, not sure what... Anyway thanks for the help, but everything is good now!
June 25, 20179 yr Author Also, one more thing. I have two nics and one of them isn't plugged in so that would probably explain the issues with eth1...
Archived
This topic is now archived and is closed to further replies.