I have installed a new motherboard/CPU in my main pc's windows build. This machine had no problem connecting to the server before. Windows installed new drivers and had to be activated again due to the amount of hardware changes. After completion, I am not able to map drives or reach the server conventionally. The only connection I can establish is via ip address. I used to access the server with "tower/". Any clues

unraid.txt

Do you have unRAID set to be Local master in SMB settings? What about the Workgroup settings? You need to have them all on the same workgroup.

Should it be local master? It currently is not.

Setting the local master to yes didn't seem to help. My surface is connected via wifi and is in the workgroup working fine. The pc is wired and is in the workgroup too, but no joy.

Is unRAID in the workgroup? It should be also if it's not.

 

Another thing you can try is shutting down everything except unRAID to allow it to assume the role of Local Master. One of the other computers may be holding onto it.

 

Also, everything on the network should be using the same gateway and subnet. What is the IP address of your unRAID and your Surface?

I will try shutting everything else down and restarting the server. I have lots of stuff that can access it. Is there a limit?

 

 

non-working pc = 192.168.1.148 Subnet 255.255.255.0

Working surface = 192.168.1.140 subnet 255.255.255.0

unraid                = 192.168.1.103 subnet 255.255.255.0

No luck. I do have another interesting behavior that may help. When I try to access by just typing "tower/" in my address bar, I get the green ball in the web page tab but "//tower/ is not available". Also, in the middle of the page it says "ERR_NAME_NOT_RESOLVED". Any more suggestions?

Is everything using the same DNS?

Can you get to it by IP?  //192.168.1.103

Yes

That was Yes to the IP question. I dont know how to verify the DNS question.

That was Yes to the IP question. I dont know how to verify the DNS question.

The DNS question has a link to how to get the DNS.

Thanks for that DNS info. The machine that is having problems has the same DNS as the machine that does not. Its 192.168.1.1 that is being handled by my DD-WRT router I guess.

What about netbios over tcp/ip? It is disabled on the "bad" machine and enabled on the one that works.

I reinstalled windows. All is good now.