Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Cannot write to network drive although in same Homegroup


12 Mar 2014   #1

Microsoft Windows 7 Professional 64-Bit 7601 Multiprocessor Free Service Pack 1
 
 
Cannot write to network drive although in same Homegroup

Dear forum,

I have a very simple network. Two desktop PCs - PC1 and PC2 - connected directly with each other via an ethernet cable (also having a WLAN connection) and one laptop connected only via WLAN. PC1 has a mapped network drive that PC3 should be able to not only read from, but write to also.

From the laptop, I can RDP into PC1 and PC2 to control them - but I cannot write files to PC1's shared network drive Z from the laptop, although the permissions on PC1 are set so I should be able to. All three computers are in the same Homegroup.

Any hints pointing me in the right direction are much appreciated!

PC1 (desktop PC connected directly to PC2 via ethernet, also has WLAN connection)
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Windows\system32>ipconfig /all
Windows-IP-Konfiguration
Hostname . . . . . . . . . . . . : PC1
Primäres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Nein
Ethernet-Adapter LAN-Verbindung:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Intel(R) 82579V Gigabit Network Connection
Physikalische Adresse . . . . . . : 54-04-A6-17-FE-B7
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::49cc:d0fb:caef:e4e1%13(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.2.2(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.2.1
DHCPv6-IAID . . . . . . . . . . . : 357827750
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-1A-91-20-87-F8-D1-11-61-4F-10
DNS-Server . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS über TCP/IP . . . . . . . : Aktiviert
Drahtlos-LAN-Adapter Drahtlosnetzwerkverbindung:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Atheros AR9285 Wireless Network Adapter
Physikalische Adresse . . . . . . : F8-D1-11-61-4F-10
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::1cc5:1796:8186:c993%11(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.2.108(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Lease erhalten. . . . . . . . . . : Freitag, 28. Februar 2014 09:00:03
Lease läuft ab. . . . . . . . . . : Samstag, 22. März 2014 04:38:40
Standardgateway . . . . . . . . . : 192.168.2.1
DHCP-Server . . . . . . . . . . . : 192.168.2.1
DHCPv6-IAID . . . . . . . . . . . : 200855825
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-1A-91-20-87-F8-D1-11-61-4F-10
DNS-Server . . . . . . . . . . . : 192.168.2.1
NetBIOS über TCP/IP . . . . . . . : Aktiviert
Tunneladapter isatap.{F9985EB4-738B-4F4C-8CFD-F13B2BDF2C0B}:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Tunneladapter Teredo Tunneling Pseudo-Interface:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Tunneladapter isatap.{DC9D804D-DE76-44E2-8E88-04F0FB7D13CC}:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #2
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja

PC2 (desktop PC connected directly to PC1 via ethernet, also has WLAN connection)
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Windows\system32>ipconfig /all
Windows-IP-Konfiguration
Hostname . . . . . . . . . . . . : PC2
Primäres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Nein
Ethernet-Adapter LAN-Verbindung:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Intel(R) 82579V Gigabit Network Connection
Physikalische Adresse . . . . . . : 54-04-A6-49-7B-C3
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::34a0:5c8c:e400:1983%12(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.2.3(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.2.1
DHCPv6-IAID . . . . . . . . . . . : 357827750
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-16-97-FD-A0-B0-48-7A-C3-A9-6B
DNS-Server . . . . . . . . . . . : 192.168.2.1
NetBIOS über TCP/IP . . . . . . . : Aktiviert
Drahtlos-LAN-Adapter Drahtlosnetzwerkverbindung:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : TP-LINK Wireless N Adapter
Physikalische Adresse . . . . . . : B0-48-7A-C3-A9-6B
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::b4cb:cfd3:fffd:335c%11(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.2.107(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Lease erhalten. . . . . . . . . . : Donnerstag, 27. Februar 2014 14:59:33
Lease läuft ab. . . . . . . . . . : Mittwoch, 19. März 2014 15:04:12
Standardgateway . . . . . . . . . : 192.168.2.1
DHCP-Server . . . . . . . . . . . : 192.168.2.1
DHCPv6-IAID . . . . . . . . . . . : 246433914
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-16-97-FD-A0-B0-48-7A-C3-A9-6B
DNS-Server . . . . . . . . . . . : 192.168.2.1
NetBIOS über TCP/IP . . . . . . . : Aktiviert
Tunneladapter Reusable ISATAP Interface {4E919AF4-7C43-49F1-BE1C-C87C84C41845}:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Tunneladapter Teredo Tunneling Pseudo-Interface:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
IPv6-Adresse. . . . . . . . . . . : 2001:0:9d38:6ab8:24c7:200c:3f57:fd94(Bevorzugt)
Verbindungslokale IPv6-Adresse . : fe80::24c7:200c:3f57:fd94%13(Bevorzugt)
Standardgateway . . . . . . . . . : ::
NetBIOS über TCP/IP . . . . . . . : Deaktiviert
Tunneladapter isatap.{8BDCEEF8-4C7A-4428-866B-915A70A74AAE}:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #2
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Tunneladapter Reusable ISATAP Interface {578E022B-2BB5-46D2-BE65-52809A973828}:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #3
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Tunneladapter isatap.{49CBF0C7-A10D-472F-A0EC-686779947343}:
Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter #4
Physikalische Adresse . . . . . . : 00-00-00-00-00-00-00-E0
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja

PC3 (laptop with WLAN connection only)
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : PC3
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 14-10-9F-DA-3E-2E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11n Network Adapter
Physical Address. . . . . . . . . : 14-10-9F-DA-3E-2D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::fd9e:19ae:77e3:69e6%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.2.113(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Mittwoch, 12. März 2014 03:41:08
Lease Expires . . . . . . . . . . : Samstag, 22. März 2014 08:09:34
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DHCPv6 IAID . . . . . . . . . . . : 236195999
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-5E-58-55-14-10-9F-DA-3E-2D
DNS Servers . . . . . . . . . . . : fe80::1%11
192.168.2.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter 6TO4 Adapter:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 13:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:90d7:349a:20fb:26a0:2673(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::349a:20fb:26a0:2673%21(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{8E980B6E-142D-4833-A5E1-32B66C8A8D71}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{EA460696-99CE-4A07-8DC0-40D28D014044}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


My System SpecsSystem Spec
.

12 Mar 2014   #2

Windows 7 Ult, Windows 8.1 Pro,
 
 

I'm wondering why you connected those machines using an Ethernet cable when you already have a router?

I can't think of any valid reason for doing this when these machines are already connected to a router with a common gateway.

As for the drive sharing issue, it's usually required to share the drive via the instructions in the following link.

HDD sharing
My System SpecsSystem Spec
12 Mar 2014   #3

Microsoft Windows 7 Professional 64-Bit 7601 Multiprocessor Free Service Pack 1
 
 

The two desktop PCs are constantly swapping much data back and forth. They are rendering light simulations. A WLAN connection was much too slow.

Thanks for the link; I shall use these instructions for the sharing aspect.
My System SpecsSystem Spec
.


13 Mar 2014   #4

Windows 7 Ult, Windows 8.1 Pro,
 
 

Quote   Quote: Originally Posted by Useless User View Post
The two desktop PCs are constantly swapping much data back and forth. They are rendering light simulations. A WLAN connection was much too slow.

Thanks for the link; I shall use these instructions for the sharing aspect.


Edit: sorry I had trouble envisioning this particular network set up, I figured out that you meant the machines were only connectable to the router through wireless but were close enough to each other in order to run a wire between them so as to transfer files faster or run the light program, I get it finally!
My System SpecsSystem Spec
13 Mar 2014   #5

Microsoft Windows 7 Professional 64-Bit 7601 Multiprocessor Free Service Pack 1
 
 

I prioritised Ethernet over WLAN with some help from one of the threads here. The WLAN router has three Ethernet sockets but is in a bad location. The sharing works as it should now, which is great. Not as straightforward as I'd thought at first.
My System SpecsSystem Spec
13 Mar 2014   #6

Windows 7 Ult, Windows 8.1 Pro,
 
 

Quote   Quote: Originally Posted by Useless User View Post
I prioritised Ethernet over WLAN with some help from one of the threads here. The WLAN router has three Ethernet sockets but is in a bad location. The sharing works as it should now, which is great. Not as straightforward as I'd thought at first.
Yes you can play around with the metric to set network connection priorities although Windows typically favors the wired connection over the wireless.

Thanks for letting me know the security tab adjustments worked to allow access.

There is also local security policy that allows Windows to connect both wired and wireless at start up, I do this just for testing wireless settings etc.


Attached Thumbnails
Cannot write to network drive although in same Homegroup-group-policy-using-two-connections-once.png  
My System SpecsSystem Spec
Reply

 Cannot write to network drive although in same Homegroup




Thread Tools



Similar help and support threads for2: Cannot write to network drive although in same Homegroup
Thread Forum
homegroup not work - network drive can't remember - please help Network & Sharing
Flaky write access to server drive in company network Network & Sharing
Difference between Homegroup and Mapping a Network Drive? Network & Sharing
write file denied on homegroup Network & Sharing
Can't write to Win7 c: Drive across network Network & Sharing

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 03:16 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33