S
Sheen Ismhael A. Lim
I have synology nas that is not accessable on a Server 2016 but not on Server 2012.
Synology NAS:
NAS01
Server 2016 Servers
Server01
Server02
Server 2012 R2 Servers
Server03
Server04
Server 2016 servers are connected to a PortGroup with VLAN 400 in ESXi vSwitch
Server 2012 servers are connected to a PortGroup with VLAN 50 in ESXi Switch.
VMs in the Server 2016 group can access the synology https://nas01.itfellas.internal and \\nas01.itfellas.internal\backups
However, Vms in the Server 2012 servers cannot access them. But I can tell from the network perspective that those VM in the Server 2012 group is can reach nas01.itfellas.internal and is resolving to the correct IP.
The servers on Server 2016 are in a domain, however servers on 2012 group are on a workgroup.
I have tried disable the firewall on the Server 2012 group but it is not loading \\nas01.itfellas.internal\backups, when visiting it from Windows Explorer, it asks for credentials, accepts the credentials but never loads the contents.
On the server 2012 SMBClient event logs, i see alot of the events in the following order.
A request timed out because there was no response from the server.
Event:30809
Log name: Microsoft-Windows-SMBClient/Connectivity
Server name: \nas01.itfellas.internal
Session ID:0x8CC75ED2
Tree ID:0xBD60006B
Message ID:0x5
Command: Create
Guidance:
The server is responding over TCP but not over SMB. Ensure the Server service is running and responsive, and the disks do not have high per-IO latency, which makes the disks appear unresponsive to SMB. Also, ensure the server is responsive overall and not paused; for instance, make sure you can log on to it.
Event:30805
Log name: Microsoft-Windows-SMBClient/Connectivity
The client lost its session to the server.
Error: {Device Timeout}
The specified I/O operation on %hs was not completed before the time-out period expired.
Server name: \nas01.itfellas.internal
Session ID: 0x8CC75ED2
Guidance:
If the server is a Windows Failover Cluster file server, then this message occurs when the file share moves between cluster nodes. There should also be an anti-event 30806 indicating the session to the server was re-established. If the server is not a failover cluster, it is likely that the server was previously online, but it is now inaccessible over the network.
Event:30807
Log name: Microsoft-Windows-SMBClient/Connectivity
The connection to the share was lost.
Error: {Device Timeout}
The specified I/O operation on %hs was not completed before the time-out period expired.
Share name: \nas01.itfellas.internal\backups
Session ID: 0x8CC75ED2
Tree ID: 0xBD60006B
Guidance:
If the server is a Windows Failover Cluster file server, then this message occurs when the file share moves between cluster nodes. There should also be an anti-event 30808 indicating the session to the server was re-established. If the server is not a failover cluster, it is likely that the server was previously online, but it is now inaccessible over the network.
Event:30806
Log name: Microsoft-Windows-SMBClient/Connectivity
The client re-established its session to the server.
Server name: \nas01.itfellas.internal
Server address: 10.216.114.72:445
Session ID: 0x85E8F344
Guidance:
You should expect this event if there was a previous event 30805, but the client successfully resumed the cached connection before the timeout expired.
Event:30808
Log name: Microsoft-Windows-SMBClient/Connectivity
The connection to the share was re-established.
Share name: \nas01.itfellas.internal\backups
Server address: 10.216.114.72:445
Session ID: 0x85E8F344
Tree ID: 0x864F89E8
Guidance:
You should expect this event if there was a previous event 30807, but the client successfully resumed the cached connection before the timeout expired.
From the nas01.itfellas.internal management portal, i can see a connection entry coming from the IP address of the server from the Server 2012 group. I have ruled out that this is not a AV or Firewall issue because I disabled them during testing.
For God, and Country.
Continue reading...
Synology NAS:
NAS01
Server 2016 Servers
Server01
Server02
Server 2012 R2 Servers
Server03
Server04
Server 2016 servers are connected to a PortGroup with VLAN 400 in ESXi vSwitch
Server 2012 servers are connected to a PortGroup with VLAN 50 in ESXi Switch.
VMs in the Server 2016 group can access the synology https://nas01.itfellas.internal and \\nas01.itfellas.internal\backups
However, Vms in the Server 2012 servers cannot access them. But I can tell from the network perspective that those VM in the Server 2012 group is can reach nas01.itfellas.internal and is resolving to the correct IP.
The servers on Server 2016 are in a domain, however servers on 2012 group are on a workgroup.
I have tried disable the firewall on the Server 2012 group but it is not loading \\nas01.itfellas.internal\backups, when visiting it from Windows Explorer, it asks for credentials, accepts the credentials but never loads the contents.
On the server 2012 SMBClient event logs, i see alot of the events in the following order.
A request timed out because there was no response from the server.
Event:30809
Log name: Microsoft-Windows-SMBClient/Connectivity
Server name: \nas01.itfellas.internal
Session ID:0x8CC75ED2
Tree ID:0xBD60006B
Message ID:0x5
Command: Create
Guidance:
The server is responding over TCP but not over SMB. Ensure the Server service is running and responsive, and the disks do not have high per-IO latency, which makes the disks appear unresponsive to SMB. Also, ensure the server is responsive overall and not paused; for instance, make sure you can log on to it.
Event:30805
Log name: Microsoft-Windows-SMBClient/Connectivity
The client lost its session to the server.
Error: {Device Timeout}
The specified I/O operation on %hs was not completed before the time-out period expired.
Server name: \nas01.itfellas.internal
Session ID: 0x8CC75ED2
Guidance:
If the server is a Windows Failover Cluster file server, then this message occurs when the file share moves between cluster nodes. There should also be an anti-event 30806 indicating the session to the server was re-established. If the server is not a failover cluster, it is likely that the server was previously online, but it is now inaccessible over the network.
Event:30807
Log name: Microsoft-Windows-SMBClient/Connectivity
The connection to the share was lost.
Error: {Device Timeout}
The specified I/O operation on %hs was not completed before the time-out period expired.
Share name: \nas01.itfellas.internal\backups
Session ID: 0x8CC75ED2
Tree ID: 0xBD60006B
Guidance:
If the server is a Windows Failover Cluster file server, then this message occurs when the file share moves between cluster nodes. There should also be an anti-event 30808 indicating the session to the server was re-established. If the server is not a failover cluster, it is likely that the server was previously online, but it is now inaccessible over the network.
Event:30806
Log name: Microsoft-Windows-SMBClient/Connectivity
The client re-established its session to the server.
Server name: \nas01.itfellas.internal
Server address: 10.216.114.72:445
Session ID: 0x85E8F344
Guidance:
You should expect this event if there was a previous event 30805, but the client successfully resumed the cached connection before the timeout expired.
Event:30808
Log name: Microsoft-Windows-SMBClient/Connectivity
The connection to the share was re-established.
Share name: \nas01.itfellas.internal\backups
Server address: 10.216.114.72:445
Session ID: 0x85E8F344
Tree ID: 0x864F89E8
Guidance:
You should expect this event if there was a previous event 30807, but the client successfully resumed the cached connection before the timeout expired.
From the nas01.itfellas.internal management portal, i can see a connection entry coming from the IP address of the server from the Server 2012 group. I have ruled out that this is not a AV or Firewall issue because I disabled them during testing.
For God, and Country.
Continue reading...