Unable to access the NAS SMB share following router or gateway upgrade.

F5F Stay Refreshed Hardware Desktop Unable to access the NAS SMB share following router or gateway upgrade.

tacgun
Member

10-18-2016, 02:18 PM

Hello, I just upgraded my Xfinity gateway and noticed I can't connect to my NAS via the TRunas in a Proxmox VM. The SMB share seems fine, but I keep getting an error. Please help me resolve this.

tacgun

10-18-2016, 02:18 PM #1

Hello, I just upgraded my Xfinity gateway and noticed I can't connect to my NAS via the TRunas in a Proxmox VM. The SMB share seems fine, but I keep getting an error. Please help me resolve this.

Foxson
Member

155

10-19-2016, 11:23 PM

Did you disable any services that could impact SMB connections? This is typically done in the VM to ensure proper configuration and security.

Foxson

10-19-2016, 11:23 PM #2

Did you disable any services that could impact SMB connections? This is typically done in the VM to ensure proper configuration and security.

WebsYT
Junior Member

10-20-2016, 10:46 PM

None of the services were altered; everything runs in a VM. It was simpler for me to set up Truespan, but that shouldn’t be the issue.

WebsYT

10-20-2016, 10:46 PM #3

None of the services were altered; everything runs in a VM. It was simpler for me to set up Truespan, but that shouldn’t be the issue.

_xxtarget_xx
Member

10-20-2016, 11:07 PM

Disable these services: Network Discovery Function Discovery (2) IPv6. If the issue persists, reinstall Truenas or adjust the VM settings to resolve network problems.

_xxtarget_xx

10-20-2016, 11:07 PM #4

Disable these services: Network Discovery Function Discovery (2) IPv6. If the issue persists, reinstall Truenas or adjust the VM settings to resolve network problems.

carraboy31
Member

117

10-21-2016, 12:44 AM

I replaced then reinstated the network device in the VM, which resolved the problem. Keep in mind it may affect the server if you don<|pad|>'s not configured statically.

carraboy31

10-21-2016, 12:44 AM #5

I replaced then reinstated the network device in the VM, which resolved the problem. Keep in mind it may affect the server if you don<|pad|>'s not configured statically.