Qnap wireless on PC but not wired

[andrei.angelin]

Hi

Dont know what triggered it but out of nowhere, my PC can only see the QNAP on wifi. All other devices e.g. apple tv can see it on wired. But PC no.

I have the Netgear Genie CG3000v2.

And a QNAP 412.

What could be causing this, really stumped!?

[dolbyman]

firewall settings on windows ?

maybe wifi allowes finding lan devices but lan connection not

[andrei.angelin]

Can someone help me?

I have been searching high and wide.

Cant connect when ethernet is connected. But wifi all good.

Stumped. No idea what is going on?

Can someone help!!!!

[schumaku]

Andrei,

Permitting the NAS and the PC is configured (typically by DHCP form the CG3000v2 router I guess) into the very same TCP/IP subnetwork, permitting the LAN switch ports on the CG3000v2 are fully transparent (including broadcast), there is not much we can help here.

Copy-paste the output of the Windows system (while connected to one of the CG3000v2 LAN ports) cmd ipconfig ...

C:\> ipconfig
...

...and from the NAS (CG3000v2 connected, too) shell ifconfig...

[~] # ifconfig
...

Let's see if there is some obvious.

-Kurt

[andrei.angelin]

PC Information:

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80:3c12:ee25:b100%4
IPv4 Address. . . . . . . . . . . : 192.168.0.19
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::7415:89ff:fe6e:d8d0%4
192.168.0.1

Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::8532:d4c5:9fe8:963%10
IPv4 Address. . . . . . . . . . . : 192.168.0.16
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

QNAP Information - I cant even login via putty. It says Network Error: Software Caused Connection Abort

This is whilst I am logged in via iexplorer to the web admin page.

[schumaku]

QNAP Information - I cant even login via putty. It says Network Error: Software Caused Connection Abort

Same with the Windows system connected to the WiFi, or only of plugged to the Ethernet?

Can't reach the NAS Web UI either?

SSH (and telnet) is enabled in the NAS Control Panel?

Disable the Wireless for the moment while connected to the CG3000v2 Gigabit Ethernet - just to ensure no 3rd party firewall does play games with us here.

[andrei.angelin]

Yes.

Now I have tried two things tonite.

1. I have my work laptop connected on hard connection LAN.
2. I have my domestic laptop connected on wifi.
3. My Apple tv has full access to the media content via the apple tv media app.

Both can access the QNAP web page and browse via the exporer.

But none recognise the QNAP as an active drive.

SSH and now telnet are enabled in the Control Panel.

My domestic laptop has all firewalls off, including windows and my anti virus stuff.

Another advancement is that I have now Puttied in and done if config.

Capture.JPG

[schumaku]

But none recognise the QNAP as an active drive.

All right, This could be caused by the NetBIOS name resolution problem latent on the Marvell Kirwood units since the recent QTS 4.3.3 builds.

Since you have SSH access now, give a try and restart SAMBA on your TS-412 using

Code: Select all

/etc/init.d/smb.sh restart

Will the NAS now show up as a computer/system?

[andrei.angelin]

You know come to think of it I feel as though this happened when I updated software.

Tried your suggestion. Nothing. Wifi can access via web portal page, but not browse via explorer.

LAN Nothing! Now I cant even connect via portal page.

Restart.JPG

Still pings though

ping.JPG

But nothing will detect it when it is on LAN

Capture.JPG

Why is it broadcasting on 192.168.0.255? Shouldl that not be the same as the gateway?

[andrei.angelin]

Nothing?

[Moogle Stiltzkin]

Can someone help me?

I have been searching high and wide.

Cant connect when ethernet is connected. But wifi all good.

Stumped. No idea what is going on?

Can someone help!!!!

Nothing?

faq link in sig below to create helpdesk ticket in case you hadn't yet expect reply from them within 24 hours after ticket.

[schumaku]

As I wrote before: This could be caused by the NetBIOS name resolution problem latent on the Marvell Kirkwood units since the recent QTS 4.3.3 builds.

Strange Qfinder fails to discover the NAS now, too - or is this again just on the wired network?

On the 192.168.0.0/24 network (mask 255.255.255.0) the broadcast address must be 192.168.0.255 - it's derived direct from the network mask.

faq link in sig below to create helpdesk ticket in case you hadn't yet expect reply from them within 24 hours after ticket.

Not sure what QNAP customer service can do if the NAS - always connected to the router GbE network port - is only reachable and workable from the router wireless, but not from the router's other GbE switch ports.

My trust in Netgear consumer routers is limited (nicely speaking), the impression is baldy hurt since we're fighting with plenty of odd issues on Netgear flagship R9000 (Nighthawk X10) and discovering the DM200 "DSL Modem" does block incoming Internet->LAN traffic.

[SpinalTap]

Hi

Dont know what triggered it but out of nowhere, my PC can only see the QNAP on wifi. All other devices e.g. apple tv can see it on wired. But PC no.

I have the Netgear Genie CG3000v2.

And a QNAP 412.

What could be causing this, really stumped!?

Hi Andrei,

Did you ever find a solution? I am having the same problem. It started occurring when I activated SMB, but now occurs regardless of whether SMB is active or not.

[SpinalTap]

Hi

Dont know what triggered it but out of nowhere, my PC can only see the QNAP on wifi. All other devices e.g. apple tv can see it on wired. But PC no.

I have the Netgear Genie CG3000v2.

And a QNAP 412.

What could be causing this, really stumped!?

Hi Andrei,

Did you ever find a solution? I am having the same problem. It started occurring when I activated SMB, but now occurs regardless of whether SMB is active or not.

I think that I found the problem. For some reason when I was activating SMB, QNAP was adding the IP of my desktop to the ban list. When I would switch to WiFi, it was of course using a different IP and was therefore being let in. I was able to regain access over the wired network by removing the IP address from the ban list in the QNAP Security control panel.