Smart Console Remote Users Mapping Drives via Samba
Overview
Users attempting to use Smart Console remotely (such as through a Virtual Private Network (VPN)) need to be able to map the shared drive for file updates through WPKG, Voice-With-A-Smile greetings local download, and other file syncing functionality. If these functions are working for Smart Console users on-site, but not for remote users, the issue likely requires edits to the Samba configuration to allow access from the subnet(s) associated with the VPN.
Goal
After completing this how-to you will understand how to add additional allowed subnets to the Samba drive mapping configuration.
First Step
Begin by determining the subnet the remote user is appearing on. This can usually be determined using the Windows Command Prompt utility via the ipconfig -all command, which will reveal network details:
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\Users\[username]>ipconfig -all
Second Step
After determining the subnet of the affected workstation, connect to the organization's primary web server, login as root, and navigate to the folder containing the Samba configuration file:
[root@udbcspokwb01 ~]# cd /etc/samba
Third Step
Back up the existing Samba configuration file:
[root@udbcspokwb01 samba]# cp smb.conf smb.conf.backup
Fourth Step
Using vi, open the configuration file for editing:
[root@udbcspokwb01 samba]# vi smb.conf
Fifth Step
Scroll through the document to the "Network Related Options" section, and edit the "hosts allow" section (highlighted) with the additional subnet information:
# ----------------------- Network Related Options -------------------------
#
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
#
# server string is the equivalent of the NT Description field
#
# netbios name can be used to specify a server name not tied to the hostname
#
# Interfaces lets you configure Samba to use multiple interfaces
# If you have multiple network interfaces then you can list the ones
# you want to listen on (never omit localhost)
#
# Hosts Allow/Hosts Deny lets you restrict who can connect, and you can
# specifiy it as a per share option as well
#
workgroup=amcomlocal
server string=Amcom
; netbios name = MYSERVER
; interfaces = lo eth0 192.168.12.2/24 192.168.13.2/24
hosts allow = 127. 10. 159.251.
What's Next
This should resolve the issue. This process does not usually require a restart of the smb service, however you can check the service status with the following:
[root@udbcspokwb01 amcom]# service smb status
smbd (pid 6555) is running...
nmbd (pid 6558) is running...