Project

General

Profile

Bug #26381

Updated IP address on SMB shares will not apply until after FreeNAS reboot.

Added by Shawn Shank almost 3 years ago. Updated almost 3 years ago.

Status:
Closed: Insufficient Info
Priority:
No priority
Assignee:
Timur Bakeyev
Category:
OS
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

Vm in ESXI 6.5
2V cores of (E3-1230 v3)
8GB ram LOCKED
RaidZ2 - 9x Red NAS Hard Drive WD30EFRX 3TB.
1x WD purple 3TB
LSI Internal SATA/SAS 9211-4i.
Intel RAID Twenty-four port Expander Card RES2SV240

ChangeLog Required:
No

Description

I have a slight issue with my SMB shares that I update quite a bit. This happens on all shares.
The only thing that I typically want to update is the IP addresses allowed to access a particular share. For example I want to update my File storage share to a new ipv4 so I change 10.0.0.50 to 10.0.0.60 and select okay. I then try and access the share on the computer running on that .60 address. FreeNAS will not allow that computer to access the share using the correct username and password for the share. The only way that I can get a connection after updating the ipv4 in FreeNAS is to reboot FreeNAS I have tried to stop SMB service and restart it and that doesn't work.

Im currently running FreeNAS version ( FreeNAS-11.0-RELEASE (a2dc21583) )

https://forums.freenas.org/index.php?threads/updated-ip-address-on-smb-shares-will-not-apply-until-after-freenas-reboot.58738/

Associated revisions

Revision deecb1d2 (diff)
Added by John Hixson almost 3 years ago

Update samba port to use interal PIDL Ticket: #26381

Revision d63d4692 (diff)
Added by John Hixson over 2 years ago

Update samba port to use interal PIDL Ticket: #26381

Revision 3514cad0 (diff)
Added by John Hixson over 2 years ago

Update samba port to use interal PIDL Ticket: #26381

Revision 7da3f1b8 (diff)
Added by John Hixson over 2 years ago

Update samba port to use interal PIDL Ticket: #26381

Revision 066711a4 (diff)
Added by John Hixson almost 2 years ago

Update samba port to use interal PIDL Ticket: #26381

Revision c7eaed9d (diff)
Added by John Hixson almost 2 years ago

Update samba port to use interal PIDL Ticket: #26381

Revision f4ba23c1 (diff)
Added by John Hixson almost 2 years ago

Update samba port to use interal PIDL Ticket: #26381

Revision b9d3bfca (diff)
Added by John Hixson almost 2 years ago

Update samba port to use interal PIDL Ticket: #26381

History

#1 Updated by Dru Lavigne almost 3 years ago

  • Assignee changed from Release Council to William Grzybowski

William: please pass to John or Timur if this is more of an SMB issue than a services/middleware issue.

#2 Updated by William Grzybowski almost 3 years ago

  • Assignee changed from William Grzybowski to Timur Bakeyev

#3 Updated by Dru Lavigne almost 3 years ago

  • Target version set to 11.1

#4 Avatar?id=14398&size=24x24 Updated by Kris Moore almost 3 years ago

  • Target version changed from 11.1 to 11.1-U1

#5 Updated by Timur Bakeyev almost 3 years ago

  • Status changed from Unscreened to Screened

#6 Updated by Timur Bakeyev almost 3 years ago

That sounds really strange...

Can you test with this from the command line/SSH terminal on the FreeNAS?

Before changing the access list to the share save output of the command to the file:

# testparm -vs > output1.txt

Change access list as necessary and save the changes. Run again:

# testparm -vs > output2.txt

Compare those outputs with the diff command:

# diff -udp output1.txt output2.txt

Put the results to the ticket.

Check, that newly added machine can(not) access the share. Check it is coming from the IP address that showed up in the diff result.

Run:

# service samba_server restart

Check if now newly added machine/IP can(not) access the share. In general, this should be enough.

If it's still can not:

# service samba_server stop
# pgrep -lf smbd

The last command shouldn't give you any output. If it does... Then something goes wrong and there are stale smbd processes remain.

# service samba_server start

Check again, if the newly added machine can access share.

Please, provide detailed report did all those commands work and at what step you(hopefully) got access to the share.

#7 Avatar?id=13649&size=24x24 Updated by Ben Gadd almost 3 years ago

  • Status changed from Screened to 15

#9 Updated by Dru Lavigne almost 3 years ago

  • Status changed from 15 to Closed: Insufficient Info
  • Target version changed from 11.1-U1 to N/A

Shawn: closing out. If it is still an issue with 11.1, please attach a debug from the updated system to this ticket.

Also available in: Atom PDF