SOLVED Suddenly cannot connect from Win7

[marcevan]

I applied the latest stable to 9.3 today and then later on:

1. Win7 cannot connect to network name of freenas which it can find in windows explorer
2. Win7 cannot connect to IP address of freenas

For network error I get 0x80070035

I went to my basement PC (Win 8.1) and alls fine.

Anyone else lose Win7 connectivity with latest update? And I suppose this needs a rollback function in FreeNAS now.

 

[Bidule0hm]

I applied the last update too (FreeNAS-9.3-STABLE-201503071634) and no problem.

Guess what? there is a rollback function for the system updates :)

 

[marcevan]

Ah after seeing the errors in console I checked CIFS service.

It had no minimum level but Samba 3.00 for maximum level.

Win7 uses Samba 2
Win8 uses Samba 3

I entered Samba 2 as minimum level and suddenly it worked.

Not sure what update removed the minimum level but that was it.

 

[Ericloewe]

Ah after seeing the errors in console I checked CIFS service.

It had no minimum level but Samba 3.00 for maximum level.

Win7 uses Samba 2
Win8 uses Samba 3

I entered Samba 2 as minimum level and suddenly it worked.

Not sure what update removed the minimum level but that was it.

Not Samba. SMB 2 and 3, respectively.

Samba is the open-source implementation of SMB.

Samba 3 supports SMB 2 and Samba 4 supports SMB 3 (or a subset thereof).

 

[cyberjock]

You shouldn't normally have to set a minimum SMB protocol because SMB is auto-negotiate to the highest supported common factor. So yeah, what you "think" fixed it likely didn't fix a darn thing. Since it should auto-negotiate, you've potentially set yourself up for other problems because a lot of stuff still doesn't do SMB2 (like android apps, iOS apps, network scanners and printers, etc.)

I'd bet if you set the minimum back to --- that it will still work because it should have changed nothing. If it does break things than a ticket needs to be filed because something actually *is* broken.

 

[marcevan]

It wasn't ----, it was empty. I changed SMB 2 to ----- and it works fine.

Now onto other issues - latest stable train update 'fails to update'.

 

[cyberjock]

It wasn't ----, it was empty. I changed SMB 2 to ----- and it works fine.

Now onto other issues - latest stable train update 'fails to update'.

Hmm. That sounds like a bug should be filed for the SMB thing. Not sure about the fails to update as I just updated a few hours ago to a build from march 17th.

 

[marcevan]

Did.

Now I just did the latest stable train upgrade and informationally I'm seeing console message tell me:

STATUS=daemon 'smbd' finished starting up and ready to serve connectionsNo protocol supported !

What does this mean?