Windows 7 networking problems (TS-119)

[flyingflatfour]

Hi everyone,

I've been reading the forums since this morning trying to find a solution to my problem.

I've just added a Windows 7 laptop to my WLAN and am trying to map drives or at least see the NAS share's, but so far no joy.

There is another WXP laptop on the network and that's working just fine.

This is what I have done so far on the Windows Seven machine:


- manually run the Server service which was turned off
- activate file, printer, folder sharing in advanced network properties
- check the Microsoft Client was installed on the network adapter
- turn off the firewall
- share folders on the WXP machine
- configure the NAS SMB settings properly according other posts
- set all devices in the same workgroup, no domain
- windows seven configured as workgroup, home network (no domain, no homegroup)

Results:

- able to ping the NAS both with IP and device name in the command prompt
- seing the NAS with QNAP Finder, but unable to map a drive from it's interface: error message "server not found..." or something like that
- seing the NAS in the network neighbourhood but only as "other device " (UPnP I guess) + Twonky Media server showing
- unable to map any drive in windows explorer, both using NAS IP address and Device name. Browsing for shares doesn't show any other computer than the one I'm working on.
- unable to see the WXP laptop in the neighbourhood.


I have to say I'm a bit lost here, if anyone could help it would be greatly appreciated. I do think this is an issue with the Windows Seven machine, something in that Windows installation is wrong when it comes to networking...


Thanks!

[2000wolf]

Hi,

Several causes are possible:

NAS network settings:
Is the NAS member of the right workgroup?

Masterbrowser option on the NAS activated?

You didn't mention the credentials:
Do you have a the same user account / password activated on the Win 7 system AND on the NAS (there with the necessary read / write permissions)?

If nothing helps you could activate the WINS-Server on the NAS and enter it's IP in the network settings of every client. However the WINS-Server will prevent HDD spin down...

[pwilson]

Hi everyone,

I've been reading the forums since this morning trying to find a solution to my problem.

I've just added a Windows 7 laptop to my WLAN and am trying to map drives or at least see the NAS share's, but so far no joy.

There is another WXP laptop on the network and that's working just fine.

This is what I have done so far on the Windows Seven machine:


- manually run the Server service which was turned off
- activate file, printer, folder sharing in advanced network properties
- check the Microsoft Client was installed on the network adapter
- turn off the firewall
- share folders on the WXP machine
- configure the NAS SMB settings properly according other posts
- set all devices in the same workgroup, no domain
- windows seven configured as workgroup, home network (no domain, no homegroup)

Results:

- able to ping the NAS both with IP and device name in the command prompt
- seing the NAS with QNAP Finder, but unable to map a drive from it's interface: error message "server not found..." or something like that
- seing the NAS in the network neighbourhood but only as "other device " (UPnP I guess) + Twonky Media server showing
- unable to map any drive in windows explorer, both using NAS IP address and Device name. Browsing for shares doesn't show any other computer than the one I'm working on.
- unable to see the WXP laptop in the neighbourhood.


I have to say I'm a bit lost here, if anyone could help it would be greatly appreciated. I do think this is an issue with the Windows Seven machine, something in that Windows installation is wrong when it comes to netwoking...


Thanks!

Perhaps give yourself a quick refresher course, by reviewing:

[youtube=adsCxE4q-gk]QNAP NAS tutorial first time installation[/youtube]

[flyingflatfour]

Hi,

Several causes are possible:

NAS network settings:
Is the NAS member of the right workgroup?

Masterbrowser option on the NAS activated?

You didn't mention the credentials:
Do you have a the same user account / password activated on the Win 7 system AND on the NAS (there with the necessary read / write permissions)?

If nothing helps you could activate the WINS-Server on the NAS and enter it's IP in the network settings of every client. However the WINS-Server will prevent HDD spin down...

Hi, thanks for replying.

The NAS is indeed in the same workgroup as the WXP and W7 machines. Masterbrowser option is activated.
I have created a user on the NAS with same user name and password as the W7 account (administrator account on the Windows machine, regular user on the NAS, and yes read/write permissions are granted in the appropriate folders)

If WINS-Server prevents HDD spin down then I won't use it In any case there is something else here going wrong, it should be working. I'm suspecting something wrong in Samba on the Windows 7 machine, but I don't know how to fix it.

Cheersh

[flyingflatfour]

Perhaps give yourself a quick refresher course, by reviewing:

[youtube=adsCxE4q-gk]QNAP NAS tutorial first time installation[/youtube]

Hi,

It's a nice video, but I've done everything as mentioned. When I want to map a network drive in QNAP finder, I get the following message: "Network failure: the server is not found on the network. Please check the server status".

I've tried both the corresponding windows credentials and the admin one. It seems that the QNAP Finder can't even get as far as challenging the NAS to those credentials, it's simply can't talk to it.

However it sees the NAS, it's IP address, I can read it's details, log on to it's web interface, etc...

I think there is just something in Windows 7 networking that I don't understand LOL.

BTW, I tried plugging in to the router by ethernet, doesn't change the problem.

Cheers

[schumaku]

Try the NAS IP address in Internet Explorer, instead of the name, as a test:

\\192.168.12.34\

I would expect you can see all the NAS shaes then. Authentication permitting by the same username and password, access to the shares must be possible,

[flyingflatfour]

Nope, doesn't work either...

[schumaku]

So definitively something wrong with your Win 7 Microsoft File Sharing client.

Probably configured the WLAN ad a Public Network instead of a Home or Office network? Windows 7 will limit services if oyu are in a public network!

[flyingflatfour]

WLAN and LAN are both configured as Home or Office networks... you are right there is definetely something wrong

[flyingflatfour]

Any Windows 7 networking expert around?

[schumaku]

Experts answer: Have you rebooted already?

Post the output of

C:\> net config
...

C:\> net view \\[NAS-IP-ADDRESS]
...

C:\> net statistics workstation
...

C:\> ipconfig
...

[flyingflatfour]

Hi!

Just had to change W7's language from swedish to english in order to understand anything in the command prompt

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\>cd..

C:\Users>cd..

C:\> net config
The following running services can be controlled:

Workstation

The command completed successfully.


C:\> net view \\192.168.2.2
The Server service is not started.

More help is available by typing NET HELPMSG 2114.


C:\> net view \\192.168.2.2
System error 53 has occurred.

The network path was not found.


C:\> net statistics workstation
Workstation Statistics for \\


Statistics since 2012-10-15 16:24:18


Bytes received 0
Server Message Blocks (SMBs) received 19
Bytes transmitted 0
Server Message Blocks (SMBs) transmitted 0
Read operations 0
Write operations 0
Raw reads denied 0
Raw writes denied 0

Network errors 0
Connections made 0
Reconnections made 12
Server disconnects 0

Sessions started 0
Hung sessions 0
Failed sessions 0
Failed operations 0
Use count 12
Failed use count 12

The command completed successfully.


C:\> ipconfig

Windows IP Configuration


Wireless LAN adapter Trådlös ** 2:

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

Wireless LAN adapter Trådlös **:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2002:c0a8:102ddf0:79ed:6166:d5a3
Temporary IPv6 Address. . . . . . : 2002:c0a8:102bd76:a361:d498:f7cc
Link-local IPv6 Address . . . . . : fe80::ddf0:79ed:6166:d5a3%13
IPv4 Address. . . . . . . . . . . : 192.168.2.7
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::222:75ff:fe24:1484%13
192.168.2.1

Ethernet adapter ** till lokalt nätverk:

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

Tunnel adapter isatap.{02CE54EE-C956-4E07-A533-4D91BAECC7BC}:

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

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:c133f57:fdf8
Link-local IPv6 Address . . . . . : fe80::c133f57:fdf8%19
Default Gateway . . . . . . . . . :

Tunnel adapter isatap.{ED7C4997-54B7-4182-B3FE-65FE5013CFD4}:

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

Tunnel adapter 6TO4 Adapter:

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

Tunnel adapter isatap.{113D3770-1361-417F-9108-476CC1D2613D}:

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

C:\>


As you can see, the Server service was again stopped but that could be that I made a mistake by switching it to manual to run it last time. Now it's on automatic and running. Not sure what setting it should be at.

Hope this gives you the answer to my problem, thanks for helping!

[schumaku]

Misste this one:

C:\> net config workstation

Microsoft Swedish is no that difficult to understnad in case

[flyingflatfour]

There you go

I know it's not related to the adapter since I have the same problem when connected by ethernet.


C:\>net config workstation
Computer name \\
Full Computer name
User name

Workstation active on
NetBT_Tcpip_{CC63A94C-D556-4760-90FF-E6BD18C06D9A} (1C4BD6CDD475)

Software version Windows 7 Home Premium

Workstation domain
Logon domain

COM Open Timeout (sec) 0
COM Send Count (byte) 16
COM Send Timeout (msec) 250
The command completed successfully.


C:\>

[pwilson]

Workstation domain MALOU68
Logon domain AMANDASLAPTOP

This suggests that AMANDASLAPTOP lives in the "MALOU68" domain.

If this is a home network it should be in a "Workgroup" rather than a "Domain". And both your NAS and your Laptop should be in the same "workgroup".


vs.