Can't Connect to DS216+II via wifi Network

Topics including remote access and management can go here, including port forwarding, telnet, ssh, and advanced network settings.
Forum rules
1) This is a user forum for Synology users to share experience/help out each other: if you need direct assistance from the Synology technical support team, please use the following form:
https://account.synology.com/support/suppo ... p?lang=enu
2) To avoid putting users' DiskStation at risk, please don't paste links to any patches provided by our Support team as we will systematically remove them. Our Support team will provide the correct patch for your DiskStation model.
reichmaj
Trainee
Trainee
Posts: 12
Joined: Thu Nov 30, 2017 4:46 am

Can't Connect to DS216+II via wifi Network

Postby reichmaj » Thu Nov 30, 2017 5:03 am

Synology Community

Recently I have been unable to connect to my Synology DS216+II via my wifi network, and I'm at a loss. I can turn of my wifi and connect using an Ethernet cable, and I can connect to the Synology NAS using either one of my other two computers, my ipad, and my iPhone but not my newest computer. Everything was fine until ATT made some changes to my UVERSE modem to fix another problem.

Computer in question: Lenovo T460, windows 10, version 1709
NAS: DS216+II
Router/Modem: Pace 5268AC

My IP address had been 192.168.1.71 but after ATT made their changes the IP address became 192.168.1.67

I've talked with Synology (they say its a router issue). I've talked with ATT (they say its a NAS issue), and Microsoft simply reinstalled Windows 10.

For what ever reason I can't access the NAS via wifi from my Lenovo T460 (can if connected via Ethernet cable), but I can connect to the NAS with my Lenovo T430 and T520 via the wifi. So to me that rules out the NAS and Pace Modem router.

I have tried the Synology Assistant using my wifi. It sees the NAS but won't connect; and I've also tried the Web assistant. Again will only connect using the Ethernet cable not wifi?????

Anyone have any suggestions?
Last edited by reichmaj on Thu Nov 30, 2017 6:29 pm, edited 1 time in total.
Squozen
Seasoned
Seasoned
Posts: 556
Joined: Wed Jan 09, 2013 1:35 am

Re: Coan't Connect to DS216+II via wifi Network

Postby Squozen » Thu Nov 30, 2017 4:12 pm

So the IP on your computer is 192.168.1.67 - is the default gateway 192.168.1.1 and the subnet mask 255.255.255.0? What IP, gateway and mask do you get when you use an ethernet cable? Are you using DHCP on the T460?

What IP and subnet mask does the Synology have?

The Synology is connected via ethernet to one of the yellow LAN ports on your router, I'm presuming.

Have you set up IP blocking on the Synology that might be stopping your T460 connecting on wifi?
reichmaj
Trainee
Trainee
Posts: 12
Joined: Thu Nov 30, 2017 4:46 am

Re: Can't Connect to DS216+II via wifi Network

Postby reichmaj » Fri Dec 01, 2017 9:35 pm

I took the radical way out. I reformatted my hard drive and reinstalled a clean version of windows 10 and ask ATT to reset the Pace Modem/router. So one of the two or maybe both took care of the issue.

Well not quite, problem has resurfaced. Apparently when I lost access to my Synology NAS it was because AT&T had turned of (actually renamed) my 5GHz radio on their router, thus forcing my L460 (as well as my other devices to sue the 2.4 GHz radio - SSID for which they were connected to) to connect to the 2.4 GHz radio. Why that would make a difference is beyond me because all my other devices could connect to the NAS through the 2.4GHz radio. Would changing the radio affect the IP address (wouldn't think so). All I know is if I connect to the 5GHz radio on my router I can see and connect to the NAS but cannot on the 2.4GHz radio.
reichmaj
Trainee
Trainee
Posts: 12
Joined: Thu Nov 30, 2017 4:46 am

Unable to access NAS through 5268ac Router on 2.4 GHz radio

Postby reichmaj » Sun Dec 03, 2017 6:01 pm

I'm asking the same question to AT&T, Synology, and Microsoft.

Devices: Synology DS216+II NAS (Network Associated Storage device), Arris 5268ac Modem/Router (UVERSE 25/25), and Lenovo T460 Laptop.

Several weeks ago we started having internet issues, and after several AT&T phone calls, the technician "turned off" the 5GHz radio, so he said. Actually I learned what he did was to simply change the 5GHz radio name (SSID) those forcing the wifi devices to use the 2.4 GHz radio. After that occurred I could no longer access my Synology NAS, which is connected to the router via an Ethernet cable. After numerous phone calls to AT&T, Synology, and Microsoft I simply opted to reformat my harddrive (thus clean install of windows 10 v 1709) , reset the Synology NAS and UVERSE modem/router back to factory spec. That worked but all I really did was set the SSID for the 5.0 and 2.4 GHz radios to the same default name. Consequently all my devices choose the 5.0 GHz radio and the internet problem reoccurred. By this time I have a better understanding of what AT&T did in the past. So I have renamed both my 2.4GHz radio (manual set the channel to 6) and 5.0 GHz radio (manual set the channel to 48) and connected my other two laptops, my iPhone , and ipad to the 2.4 GHz radio and my Lenovo T460 to the 5GHz radio, which seem to solve my internet and NAS connection problem. However If I set my Lenovo T460 to the 2.4 GHz radio and can not longer connect to my NAS, the IP address no longer works???? SO I leave my T460 on the 5GHz radio while every thing else uses the 2.4 GHz radio. While this solve my problems I can't understand while my other two laptops, my ipad, and iPhone can connect to the NAS using either radio but my L460 (new) will only connect to my NAS via the 5.0 GHz radio. I can access the NAS (when on the 2.4 GHz radio) via Synology quick connect but not via its IP addess???
Squozen
Seasoned
Seasoned
Posts: 556
Joined: Wed Jan 09, 2013 1:35 am

Re: Unable to access NAS through 5268ac Router on 2.4 GHz radio

Postby Squozen » Tue Dec 05, 2017 5:03 pm

Why did you create a second thread for this?

Is the T460 getting an IP address when you connect on 2.4Ghz? Can you ping the gateway?

You have already eliminated the Synology as a source of the problem. And given that the other devices in your house work with the 2.4Ghz SSID I would suspect your new laptop is faulty.

One more thing I'd suggest - check that you haven't blocked any IPs in your NAS.
reichmaj
Trainee
Trainee
Posts: 12
Joined: Thu Nov 30, 2017 4:46 am

Re: Can't Connect to DS216+II via wifi Network

Postby reichmaj » Wed Dec 06, 2017 3:42 am

Second post my mistake

No problems when connected to 5GHz radio.

Yes I can ping the router when connected to the 2.4 GHz radio but when I try and ping the NAS - Destination host unreachable. Although I can connect via an Ethernet cable or through the Synology quick connect.

There have been a number of post some time ago here is one
https://forum.synology.com/enu/viewtopic.php?t=56258, and
https://social.technet.microsoft.com/Forums/en-US/fc734788-245d-4f4c-8d6b-804a3fe80c15/connecting-to-network-attached-storage?forum=win10itpronetworking, and
https://support.microsoft.com/en-us/help/10741/windows-10-fix-network-connection-issues

Regarding blocked IP address
- Control Panel - Connectivity - Security - Account - Auto Block is not checked
- I enabled it to check the Allow/Block list - empty
Squozen
Seasoned
Seasoned
Posts: 556
Joined: Wed Jan 09, 2013 1:35 am

Re: Can't Connect to DS216+II via wifi Network

Postby Squozen » Wed Dec 06, 2017 10:46 am

Ok. Next - check the IP addresses and masks you get when you connect to both radios. Are they the same? You might as well list the IP addresses, masks and gateways of the laptop (on both radios), NAS and router at this point so we can be sure there's not something else going on (rogue DHCP server in your network).

Is there any sort of internet security software on the laptop?

Also, check that your subnet masks are the same on all devices! Most likely 255.255.255.0. If one is wrong you could be losing your return path from the NAS on certain IPs.
reichmaj
Trainee
Trainee
Posts: 12
Joined: Thu Nov 30, 2017 4:46 am

Re: Can't Connect to DS216+II via wifi Network

Postby reichmaj » Wed Dec 06, 2017 11:14 pm

Internet Security McAfee, and I've tried Turing off the firewall on both the NcAfee and Router
subnet masks are the same on all devices - I think so . Not sure how to check all items

2.4 GHz Radio

Windows IP Configuration


Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Local Area Connection* 10:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : attlocal.net
IPv6 Address. . . . . . . . . . . : 2600:1700:69c0:f4d0::5f9
IPv6 Address. . . . . . . . . . . : 2600:1700:69c0:f4d0:922:95f9:d2ad:4fe4
Temporary IPv6 Address. . . . . . : 2600:1700:69c0:f4d0:f57f:fd23:158a:4152
Link-local IPv6 Address . . . . . : fe80::922:95f9:d2ad:4fe4%19
IPv4 Address. . . . . . . . . . . : 192.168.1.68
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::16ed:bbff:fe0e:b7ad%19
192.168.1.254

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:493:1f8a:97f2:2216
Link-local IPv6 Address . . . . . : fe80::493:1f8a:97f2:2216%11
Default Gateway . . . . . . . . . :

From Windows
SSID: ATT9GJx375
Protocol: 802.11n
Security type: WPA2-Personal
Network band: 2.4 GHz
Network channel: 6
IPv6 address: 2600:1700:69c0:f4d0::5f9
2600:1700:69c0:f4d0:922:95f9:d2ad:4fe4
IPv6 DNS servers: 2600:1700:69c0:f4d0::1
IPv4 address: 192.168.1.68
IPv4 DNS servers: 192.168.1.254
Manufacturer: Intel Corporation
Description: Intel(R) Dual Band Wireless-AC 8260
Driver version: 19.71.1.1
Physical address (MAC): E4-A4-71-E4-99-EA

***************************************************************************************************

5.0 GHz Radio

Windows IP Configuration


Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Local Area Connection* 10:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : attlocal.net
IPv6 Address. . . . . . . . . . . : 2600:1700:69c0:f4d0::5f9
IPv6 Address. . . . . . . . . . . : 2600:1700:69c0:f4d0:922:95f9:d2ad:4fe4
Temporary IPv6 Address. . . . . . : 2600:1700:69c0:f4d0:4c29:c33f:76b0:ab15
Link-local IPv6 Address . . . . . : fe80::922:95f9:d2ad:4fe4%19
IPv4 Address. . . . . . . . . . . : 192.168.1.68
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::16ed:bbff:fe0e:b7ad%19
192.168.1.254

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:1800:1178:97f2:2216
Link-local IPv6 Address . . . . . : fe80::1800:1178:97f2:2216%11
Default Gateway . . . . . . . . . :

From Windows
SSID: ATT9GJx375_5GHz
Protocol: 802.11ac
Security type: WPA2-Personal
Network band: 5 GHz
Network channel: 48
IPv6 address: 2600:1700:69c0:f4d0::5f9
2600:1700:69c0:f4d0:922:95f9:d2ad:4fe4
IPv6 DNS servers: 2600:1700:69c0:f4d0::1
IPv4 address: 192.168.1.68
IPv4 DNS servers: 192.168.1.254
Manufacturer: Intel Corporation
Description: Intel(R) Dual Band Wireless-AC 8260
Driver version: 19.71.1.1
Physical address (MAC): E4-A4-71-E4-99-EA

Router 2.4 GHZ

IP Address: 104.13.221.233
Subnet Mask: 255.255.252.0
Default Gateway: 104.13.220.1

Router 5.0 GHz

IP Address: 104.13.221.233
Subnet Mask: 255.255.252.0
Default Gateway: 104.13.220.1

Not sure I know how to obtain either th emask or the gateways number for the NAS but its IP address is 192.168.1.74 Now a it was some time ago (10 days or so) 192.168.1.64

What I don't understand is the computer sees and lists it under Network Computers (File Manger), when connected to the 2.5 GHz radio but will not connect - network error.
reichmaj
Trainee
Trainee
Posts: 12
Joined: Thu Nov 30, 2017 4:46 am

Re: Can't Connect to DS216+II via wifi Network

Postby reichmaj » Thu Dec 07, 2017 1:05 am

[quote="reichmaj"]Internet Security McAfee, and I've tried Turing off the firewall on both the NcAfee and Router
subnet masks are the same on all devices - I think so . Not sure how to check all items

2.4 GHz Radio

Windows IP Configuration


Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Local Area Connection* 10:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : attlocal.net
IPv6 Address. . . . . . . . . . . : 2600:1700:69c0:f4d0::5f9
IPv6 Address. . . . . . . . . . . : 2600:1700:69c0:f4d0:922:95f9:d2ad:4fe4
Temporary IPv6 Address. . . . . . : 2600:1700:69c0:f4d0:f57f:fd23:158a:4152
Link-local IPv6 Address . . . . . : fe80::922:95f9:d2ad:4fe4%19
IPv4 Address. . . . . . . . . . . : 192.168.1.68
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::16ed:bbff:fe0e:b7ad%19
192.168.1.254

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:493:1f8a:97f2:2216
Link-local IPv6 Address . . . . . : fe80::493:1f8a:97f2:2216%11
Default Gateway . . . . . . . . . :

From Windows
SSID: ATT9GJx375
Protocol: 802.11n
Security type: WPA2-Personal
Network band: 2.4 GHz
Network channel: 6
IPv6 address: 2600:1700:69c0:f4d0::5f9
2600:1700:69c0:f4d0:922:95f9:d2ad:4fe4
IPv6 DNS servers: 2600:1700:69c0:f4d0::1
IPv4 address: 192.168.1.68
IPv4 DNS servers: 192.168.1.254
Manufacturer: Intel Corporation
Description: Intel(R) Dual Band Wireless-AC 8260
Driver version: 19.71.1.1
Physical address (MAC): E4-A4-71-E4-99-EA

***************************************************************************************************

5.0 GHz Radio

Windows IP Configuration


Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Local Area Connection* 10:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : attlocal.net
IPv6 Address. . . . . . . . . . . : 2600:1700:69c0:f4d0::5f9
IPv6 Address. . . . . . . . . . . : 2600:1700:69c0:f4d0:922:95f9:d2ad:4fe4
Temporary IPv6 Address. . . . . . : 2600:1700:69c0:f4d0:4c29:c33f:76b0:ab15
Link-local IPv6 Address . . . . . : fe80::922:95f9:d2ad:4fe4%19
IPv4 Address. . . . . . . . . . . : 192.168.1.68
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::16ed:bbff:fe0e:b7ad%19
192.168.1.254

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:1800:1178:97f2:2216
Link-local IPv6 Address . . . . . : fe80::1800:1178:97f2:2216%11
Default Gateway . . . . . . . . . :

From Windows
SSID: ATT9GJx375_5GHz
Protocol: 802.11ac
Security type: WPA2-Personal
Network band: 5 GHz
Network channel: 48
IPv6 address: 2600:1700:69c0:f4d0::5f9
2600:1700:69c0:f4d0:922:95f9:d2ad:4fe4
IPv6 DNS servers: 2600:1700:69c0:f4d0::1
IPv4 address: 192.168.1.68
IPv4 DNS servers: 192.168.1.254
Manufacturer: Intel Corporation
Description: Intel(R) Dual Band Wireless-AC 8260
Driver version: 19.71.1.1
Physical address (MAC): E4-A4-71-E4-99-EA

Router 2.4 GHZ

IP Address: 104.13.221.233
Subnet Mask: 255.255.252.0
Default Gateway: 104.13.220.1

Router 5.0 GHz

IP Address: 104.13.221.233
Subnet Mask: 255.255.252.0
Default Gateway: 104.13.220.1

Not sure I know how to obtain either th emask or the gateways number for the NAS but its IP address is 192.168.1.74 Now a it was some time ago (10 days or so) 192.168.1.64

What I don't understand is the computer sees and lists it under Network Computers (File Manger), when connected to the 2.5 GHz radio but will not connect - network error.

Working through these posts
https://technet.microsoft.com/en-us/library/cc940110.aspx - and
https://forum.synology.com/enu/viewtopic.php?f=49&t=128676
sincarne
Navigator
Navigator
Posts: 975
Joined: Wed Feb 15, 2017 9:57 pm

Re: Can't Connect to DS216+II via wifi Network

Postby sincarne » Thu Dec 07, 2017 5:38 am

what happen when go to 192.168.1.64:5000 in browser? you should set your IP to static in NAS network setting so it not change.
Squozen
Seasoned
Seasoned
Posts: 556
Joined: Wed Jan 09, 2013 1:35 am

Re: Can't Connect to DS216+II via wifi Network

Postby Squozen » Thu Dec 07, 2017 11:11 am

Give the NAS a static IP with the subnet mask 255.255.255.0 and the gateway 192.168.1.254. I'd suggest 192.168.1.200. You can then connect to your router on 192.168.1.254 and change the DHCP range to only give IPs between 192.168.1.1 and 192.168.1.100, which is plenty for a home network.

You have the same IP address on both radios.

So, answer these questions:

1. Can you ping 192.168.1.254 on both radios?
2. Can you ping the NAS on both radios?

The answer to both of these should be yes! The NAS only cares about your IP address, it has no knowledge of the wifi network.

You might want to temporarily disable IPv6 on your laptop as well to eliminate it as a source of issues.
reichmaj
Trainee
Trainee
Posts: 12
Joined: Thu Nov 30, 2017 4:46 am

Re: Can't Connect to DS216+II via wifi Network

Postby reichmaj » Thu Dec 07, 2017 11:13 pm

I didn't know how to disable the IPv6 so I used this link : https://support.microsoft.com/en-us/help/929852/how-to-disable-ipv6-or-its-components-in-windows
Then I tried uncheck IPv6 via the Wi-Fi Properties dialog

Yes 5 GHz radio ... No 2.4 GHz

*********** 5.0 GHz ******************************

C:\Windows\system32>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64

Ping statistics for 192.168.1.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 4ms, Average = 2ms

C:\Windows\system32>ping 192.168.1.74

Pinging 192.168.1.74 with 32 bytes of data:
Reply from 192.168.1.74: bytes=32 time=1ms TTL=64
Reply from 192.168.1.74: bytes=32 time=3ms TTL=64
Reply from 192.168.1.74: bytes=32 time=3ms TTL=64
Reply from 192.168.1.74: bytes=32 time=3ms TTL=64

Ping statistics for 192.168.1.74:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 2ms

*********** 2.4 GHz ******************************
C:\Windows\system32>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64

Ping statistics for 192.168.1.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms

C:\Windows\system32>ping 192.168.1.74

Pinging 192.168.1.74 with 32 bytes of data:
Reply from 192.168.1.68: Destination host unreachable.
Reply from 192.168.1.68: Destination host unreachable.
Reply from 192.168.1.68: Destination host unreachable.
Reply from 192.168.1.68: Destination host unreachable.

Ping statistics for 192.168.1.74:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Disable IPv6 on nontunnel interfaces (except the loopback) and on IPv6 tunnel interface.

***************** 2.54 GHz **********************

C:\Windows\system32>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\Windows\system32>ping 192.168.1.74

Pinging 192.168.1.74 with 32 bytes of data:
Reply from 192.168.1.68: Destination host unreachable.
Reply from 192.168.1.68: Destination host unreachable.
Reply from 192.168.1.68: Destination host unreachable.
Reply from 192.168.1.68: Destination host unreachable.

Ping statistics for 192.168.1.74:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

***************** 5.0 GHz **************************
yes both
reichmaj
Trainee
Trainee
Posts: 12
Joined: Thu Nov 30, 2017 4:46 am

Re: Can't Connect to DS216+II via wifi Network

Postby reichmaj » Thu Dec 07, 2017 11:41 pm

"Give the NAS a static IP with the subnet mask 255.255.255.0 and the gateway 192.168.1.254. I'd suggest 192.168.1.200. You can then connect to your router on 192.168.1.254 and change the DHCP range to only give IPs between 192.168.1.1 and 192.168.1.100, which is plenty for a home network."

NAS Static IP set to

IP - 192.168.1.74
Mask - 255.255.255.0
Gateway - 192.168.1.254 then you suggest 192.168.1.200 - suggest to what? not sure what your suggesting

Made changes to router

Router Address 192.168.1.254
Subnet Mask 255.255.255.0
First DHCP Address 192.168.1.1
Last DHCP Address 192.168.1.100

On the 2.4 GHz radio could not connect to NAS at 192.168.1.74
**********************************************************************************************************
Ok to add more confusion. I read a blog that indicated it was unusual for a router to "act-up" after a firmware update. That's the only thing that I am aware of that changed. ATT updated my firmware at or about the time the issue started. The article indicated that a reset will usually fix any problem so I reset the router and I had access to the NAS on both radios. Ok problem solved - Not!. I was able to connect to the NAS using IP 192.168.1.80 on (1st) the 2.4 GHz radio then on the 5GHz radio. However when I went back to the 2.4 GHz radio to reconfirm it wouldn't connect. I again reset the Router and was able again to connect on the 2.4 GHz radio, and then connect on the 5.0 GHz radio, but then then when I went back to the 2.4 GHz radio no connection. So I think we have eliminated both my computer and the Synology NAS which leaves the router - would you agree?

While my initial thought was its a router issue, I don't think so. The problem is only associated with my laptop as I don't have any problems connecting to the NAS with either the 2.4 or 5GHz radios with either of my other computers , iPhone, or ipad. But I certain don't think its a Synology problem.
Squozen
Seasoned
Seasoned
Posts: 556
Joined: Wed Jan 09, 2013 1:35 am

Re: Can't Connect to DS216+II via wifi Network

Postby Squozen » Fri Dec 08, 2017 10:53 am

No, I was suggesting setting the NAS IP address to 192.168.1.200. Right now you've set it to a static IP within the DHCP range your router is assigning, which means you could get a conflict with another device on the network. Change it to 192.168.1.200 and then try to ping it from different devices on the wireless network.

Show me the output of the 'route print' command from the laptop. It doesn't think it has a route to 192.168.1.74 which makes no sense because it's on the same subnet.

Also, type 'arp -a' and show me that output. It will tell us whether the laptop knows the MAC address on the NAS (which it should if it is able to broadcast successfully). You're looking for the IP address of the NAS followed by the MAC address. Neither value should be changing as the MAC is fixed in hardware and the IP has now been set to a static value by you.
reichmaj
Trainee
Trainee
Posts: 12
Joined: Thu Nov 30, 2017 4:46 am

Re: Can't Connect to DS216+II via wifi Network

Postby reichmaj » Fri Dec 08, 2017 2:47 pm

How can the computer see a device with IP *.1.200 when I have set the range between *.1.1 and *.1.100

Any way per your request. This morning having reset my route last night and connected to the 2.4GHz radio. Computer sees NAS

Microsoft Windows [Version 10.0.16299.64]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Users\reichmaj>ping 192.168.1.200

Pinging 192.168.1.200 with 32 bytes of data:
Reply from 192.168.1.200: bytes=32 time=2ms TTL=64
Reply from 192.168.1.200: bytes=32 time=2ms TTL=64
Reply from 192.168.1.200: bytes=32 time=2ms TTL=64
Reply from 192.168.1.200: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms

C:\Users\reichmaj>route print
===========================================================================
Interface List
3...c8 5b 76 51 88 2d ......Intel(R) Ethernet Connection I219-LM
15...e4 a4 71 e4 99 eb ......Microsoft Wi-Fi Direct Virtual Adapter
9...e4 a4 71 e4 99 ea ......Intel(R) Dual Band Wireless-AC 8260
6...e4 a4 71 e4 99 ee ......Bluetooth Device (Personal Area Network)
1...........................Software Loopback Interface 1
8...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.68 50
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
192.168.1.0 255.255.255.0 On-link 192.168.1.68 306
192.168.1.68 255.255.255.255 On-link 192.168.1.68 306
192.168.1.255 255.255.255.255 On-link 192.168.1.68 306
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.1.68 306
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.1.68 306
===========================================================================
Persistent Routes:
None

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
8 331 ::/0 On-link
1 331 ::1/128 On-link
8 331 2001::/32 On-link
8 331 2001:0:4137:9e76:48d:155e:97f2:2216/128
On-link
9 306 fe80::/64 On-link
8 331 fe80::/64 On-link
8 331 fe80::48d:155e:97f2:2216/128
On-link
9 306 fe80::8e1:4a61:3f1a:c095/128
On-link
1 331 ff00::/8 On-link
9 306 ff00::/8 On-link
8 331 ff00::/8 On-link
===========================================================================
Persistent Routes:
None

C:\Users\reichmaj>
C:\Users\reichmaj>arp -a

Interface: 192.168.1.68 --- 0x9
Internet Address Physical Address Type
192.168.1.1 14-ed-bb-0e-b7-b6 dynamic
192.168.1.71 8c-fa-ba-3e-52-e4 dynamic
192.168.1.200 00-11-32-78-1b-7a dynamic
192.168.1.254 14-ed-bb-0e-b7-ad dynamic
192.168.1.255 ff-ff-ff-ff-ff-ff static
224.0.0.2 01-00-5e-00-00-02 static
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.251 01-00-5e-00-00-fb static
224.0.0.252 01-00-5e-00-00-fc static
224.0.0.253 01-00-5e-00-00-fd static
239.255.255.250 01-00-5e-7f-ff-fa static
255.255.255.255 ff-ff-ff-ff-ff-ff static

C:\Users\reichmaj>

*******************************************
Changing to the 5.0 GHz Radio, Computer sees NAS
*******************************************
Microsoft Windows [Version 10.0.16299.64]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Users\reichmaj>ping 192.168.1.200

Pinging 192.168.1.200 with 32 bytes of data:
Reply from 192.168.1.200: bytes=32 time=2ms TTL=64
Reply from 192.168.1.200: bytes=32 time=3ms TTL=64
Reply from 192.168.1.200: bytes=32 time=3ms TTL=64
Reply from 192.168.1.200: bytes=32 time=3ms TTL=64

Ping statistics for 192.168.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms

C:\Users\reichmaj>route print
===========================================================================
Interface List
3...c8 5b 76 51 88 2d ......Intel(R) Ethernet Connection I219-LM
15...e4 a4 71 e4 99 eb ......Microsoft Wi-Fi Direct Virtual Adapter
9...e4 a4 71 e4 99 ea ......Intel(R) Dual Band Wireless-AC 8260
6...e4 a4 71 e4 99 ee ......Bluetooth Device (Personal Area Network)
1...........................Software Loopback Interface 1
8...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.68 35
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
192.168.1.0 255.255.255.0 On-link 192.168.1.68 291
192.168.1.68 255.255.255.255 On-link 192.168.1.68 291
192.168.1.255 255.255.255.255 On-link 192.168.1.68 291
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.1.68 291
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.1.68 291
===========================================================================
Persistent Routes:
None

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
9 291 ::/0 fe80::16ed:bbff:fe0e:b7ad
1 331 ::1/128 On-link
8 331 2001::/32 On-link
8 331 2001:0:9d38:6ab8:204d:3d85:97f2:2216/128
On-link
9 51 2600:1700:69c0:f4d0::/60 fe80::16ed:bbff:fe0e:b7ad
9 291 2600:1700:69c0:f4d0::/64 On-link
9 291 2600:1700:69c0:f4d0::6f1/128
On-link
9 291 2600:1700:69c0:f4d0:8e1:4a61:3f1a:c095/128
On-link
9 291 2600:1700:69c0:f4d0:3191:ca88:8516:59bb/128
On-link
9 291 fe80::/64 On-link
8 331 fe80::/64 On-link
9 291 fe80::8e1:4a61:3f1a:c095/128
On-link
8 331 fe80::204d:3d85:97f2:2216/128
On-link
1 331 ff00::/8 On-link
9 291 ff00::/8 On-link
8 331 ff00::/8 On-link
===========================================================================
Persistent Routes:
None

C:\Users\reichmaj>arp -a

Interface: 192.168.1.68 --- 0x9
Internet Address Physical Address Type
192.168.1.1 14-ed-bb-0e-b7-b6 dynamic
192.168.1.200 00-11-32-78-1b-7a dynamic
192.168.1.254 14-ed-bb-0e-b7-ad dynamic
192.168.1.255 ff-ff-ff-ff-ff-ff static
224.0.0.2 01-00-5e-00-00-02 static
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.251 01-00-5e-00-00-fb static
224.0.0.252 01-00-5e-00-00-fc static
224.0.0.253 01-00-5e-00-00-fd static
239.255.255.250 01-00-5e-7f-ff-fa static
255.255.255.255 ff-ff-ff-ff-ff-ff static

C:\Users\reichmaj>

******************************
Changing back to the 2.4 GHz radio, computer does not see NAS
************************************
Microsoft Windows [Version 10.0.16299.64]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Users\reichmaj>ping 192.168.1.200

Pinging 192.168.1.200 with 32 bytes of data:
Reply from 192.168.1.68: Destination host unreachable.
Reply from 192.168.1.68: Destination host unreachable.
Reply from 192.168.1.68: Destination host unreachable.
Reply from 192.168.1.68: Destination host unreachable.

Ping statistics for 192.168.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\reichmaj>route print
===========================================================================
Interface List
3...c8 5b 76 51 88 2d ......Intel(R) Ethernet Connection I219-LM
15...e4 a4 71 e4 99 eb ......Microsoft Wi-Fi Direct Virtual Adapter
6...e4 a4 71 e4 99 ee ......Bluetooth Device (Personal Area Network)
9...e4 a4 71 e4 99 ea ......Intel(R) Dual Band Wireless-AC 8260
1...........................Software Loopback Interface 1
8...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.68 65
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
192.168.1.0 255.255.255.0 On-link 192.168.1.68 321
192.168.1.68 255.255.255.255 On-link 192.168.1.68 321
192.168.1.255 255.255.255.255 On-link 192.168.1.68 321
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.1.68 321
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.1.68 321
===========================================================================
Persistent Routes:
None

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
9 321 ::/0 fe80::16ed:bbff:fe0e:b7ad
1 331 ::1/128 On-link
8 331 2001::/32 On-link
8 331 2001:0:9d38:6ab8:204d:3d85:97f2:2216/128
On-link
9 81 2600:1700:69c0:f4d0::/60 fe80::16ed:bbff:fe0e:b7ad
9 321 2600:1700:69c0:f4d0::/64 On-link
9 321 2600:1700:69c0:f4d0:8e1:4a61:3f1a:c095/128
On-link
9 321 2600:1700:69c0:f4d0:90b2:2cd5:f060:2b53/128
On-link
9 321 fe80::/64 On-link
8 331 fe80::/64 On-link
9 321 fe80::8e1:4a61:3f1a:c095/128
On-link
8 331 fe80::204d:3d85:97f2:2216/128
On-link
1 331 ff00::/8 On-link
9 321 ff00::/8 On-link
8 331 ff00::/8 On-link
===========================================================================
Persistent Routes:
None

C:\Users\reichmaj>arp -a

Interface: 192.168.1.68 --- 0x9
Internet Address Physical Address Type
192.168.1.254 14-ed-bb-0e-b7-ad dynamic
192.168.1.255 ff-ff-ff-ff-ff-ff static
224.0.0.2 01-00-5e-00-00-02 static
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.251 01-00-5e-00-00-fb static
224.0.0.252 01-00-5e-00-00-fc static
224.0.0.253 01-00-5e-00-00-fd static
239.255.255.250 01-00-5e-7f-ff-fa static
255.255.255.255 ff-ff-ff-ff-ff-ff static

C:\Users\reichmaj>

So something happens where when changing radios.

Return to “Remote Access and Network Management”

Who is online

Users browsing this forum: No registered users and 9 guests