I just got new unifi gateway and 24 port poe switch. I reset my network config in unraid to start fresh, and now I can't reconnect using samba share.

I was trying to setup link aggregation and somewhere I broke things. I can still connect to the GUI, Winscp still works, network speed through winscp is around 20Mbs.

Plex Docker still works and Nvidia shields still have access.

Any help would be greatly appreciated

 

OS, Windows 10.

tower-diagnostics-20190708-1843.zip

OK, leave the physical network setup alone for a minimum of an hour.  (Yes, it can take that long for a SMB network to stabilize!)  While you are waiting, read this thread:

 

https://forums.unraid.net/topic/53172-windows-issues-with-unraid/

 

 

Implement the things on the first page if you have not already done so.  Then work from the last post backwards through the thread.  (WIN10 is a constantly changing target as MS tightens SMB security.)   

 

Be sure that you try    \\I.P_ADDRESS    in the address bar of Windows Explorer-- (example:   \\192.168.1.239    ) 

I installed local master, server is the master.

Still no connection to smb.

Also I saw that Nitsuj fixed his by changin DHCP to yes. How can I change this file with out pulling usb and inserting it into a pc?

 

# Generated settings:
IFNAME[0]="eth0"
PROTOCOL[0]="ipv4"
USE_DHCP[0]="no"
IPADDR[0]="192.168.1.79"
NETMASK[0]="255.255.255.0"
GATEWAY[0]="192.168.1.1"
DNS_SERVER1="8.8.8.8"
USE_DHCP6[0]="yes"
DHCP6_KEEPRESOLV="no"
SYSNICS="1"

It started Working.. I have to use IP now \\tower wont work anymore. Is their a way to fix this?

 

The only reliable way I have seen for this is to update the hosts file on the client machine to map the name to the IP address.    Microsoft keep playing round with network discovery and breaks things.

First thing, Windows will see it as \\TOWER      (This is a holdover from DOS days...)  IF you wait long enough, it might start to work.  Next thing, Make sure that the workgroup name is the same for all of the devices that are going to be using the server.  Best practice is for the Workgroup to be all caps-- i.e., WORKGROUP.  

 

Second thing, you should probably go into the setup for your router and assign your Unraid server IP address as static.  While it might work without notifying the router, it is always safer to do it.  (Particularly, since you have a 24 port switch!) 

 

Third, you can change the network settings from   Settings   >>>   Network Settings  

 

EDIT:   If you have a later version of WIN10, you will have to turn on Network Discovery as @itimpi mentioned.  You can find instructions for how to do this toward the end of the thread I pointed you to.  

Edited July 8, 20197 yr by Frank1940

Thanks again, I will double check WORKGROUP all caps on all systems. And hope this doesn't break again.

I am really beginning to dislike Windows.

I edited my post a bit so be sure to reread it. 

7 minutes ago, Frank1940 said:

First thing, Windows will see it as \\TOWER      (This is a holdover from DOS days...)  IF you wait long enough, it might start to work.  Next thing, Make sure that the workgroup name is the same for all of the devices that are going to be using the server.  Best practice is for the Workgroup to be all caps-- i.e., WORKGROUP.  

 

Second thing, you should probably go into the setup for your router and assign your Unraid server IP address as static.  While it might work without notifying the router, it is always safer to do it.  (Particularly, since you have a 24 port switch!) 

 

Third, you can change the network settings from   Settings   >>>   Network Settings  

 

EDIT:   If you have a later version of WIN10, you will have to turn on Network Discovery as @itimpi mentioned.  You can find instructions for how to do this toward the end of the thread I pointed you to.  

 

1 minute ago, AinsWorth said:

Thanks again, I will double check WORKGROUP all caps on all systems. And hope this doesn't break again.

I am really beginning to dislike Windows.

It  will be broken again.  MS is really concerned about security (mostly for the corporate clients) and SMB, as originally designed, had absolutely no security features!!!   Most of us Unraid users don't have the same type of exposure as the corporate world but we get caught in the undertow as MS has apparently decided that rather than telling the IT folks who are the true targets to turn off SMBv1 and Network Discovery, they just turn it off for everyone. 

Figures, Its always something with these companies. Sadly, you are right! I may switch to linux in the future if this keeps up.