This is just plain weird...! Here is what is happening. I have three PCs all on the same MS Home network, not password protected. Connected via Netgear router
Windows 7 x64 machine 'A' - Ethernet
Windows 7 x64 machine 'B' - Wireless only
Winxows XP SP3 laptop - Ethernet
Win7 'A' has a range of shared folders the other two can access at will throughout the day.
I can spend all day randomly accessing Win7 'A's shared folders from the XP laptop and everything is working fine. BUT If Win7 'B' accesses the shared folders on Win7 'A' then trying to access afterwards from XP laptop fails with a "//Win7APC is unavailable, contact network admin etc. etc." fault pop-up.
Doesn't matter what I do, the laptop just won't connect after Win7 'B' has been accessing 'A's files.
Looking the other way (once this fault occurs) Win7 'A' can see and access the Shared folder on the XP laptop and write and modify anything within fine..
Only solution I have found is to reboot Win7 'A' then all is well, the laptop can access again as normal.
So Win7 'B' accessing the Win7 'A' files seems to be causing the loss of access to the laptop. I should add that the accesses are not simultaneous. I have tried this with the laptop idle while 'B' accesses 'A' and then once 'B' is finished and not connected I try to access once more from the laptop - it produces the same fault. Only the rebooting of 'A' will cure it.
Any ideas why a simple folder access from another machine on the network should stop the Laptop from accessing the network? I am all out of ideas!
Cheers
J
Windows 7 x64 machine 'A' - Ethernet
Windows 7 x64 machine 'B' - Wireless only
Winxows XP SP3 laptop - Ethernet
Win7 'A' has a range of shared folders the other two can access at will throughout the day.
I can spend all day randomly accessing Win7 'A's shared folders from the XP laptop and everything is working fine. BUT If Win7 'B' accesses the shared folders on Win7 'A' then trying to access afterwards from XP laptop fails with a "//Win7APC is unavailable, contact network admin etc. etc." fault pop-up.
Doesn't matter what I do, the laptop just won't connect after Win7 'B' has been accessing 'A's files.
Looking the other way (once this fault occurs) Win7 'A' can see and access the Shared folder on the XP laptop and write and modify anything within fine..
Only solution I have found is to reboot Win7 'A' then all is well, the laptop can access again as normal.
So Win7 'B' accessing the Win7 'A' files seems to be causing the loss of access to the laptop. I should add that the accesses are not simultaneous. I have tried this with the laptop idle while 'B' accesses 'A' and then once 'B' is finished and not connected I try to access once more from the laptop - it produces the same fault. Only the rebooting of 'A' will cure it.
Any ideas why a simple folder access from another machine on the network should stop the Laptop from accessing the network? I am all out of ideas!
Cheers
J
My Computer
At a glance
Windows 7 64bit Ultimatei7 920 o/c to 3.04Ghz12Gb Corsair XMS DDR3 PC3-12800 (1600) CAS 9768Mb Nvidia Quadro FX 1800
- Computer Manufacturer/Model Number
- Scan 3XS
- OS
- Windows 7 64bit Ultimate
- CPU
- i7 920 o/c to 3.04Ghz
- Motherboard
- Asus P6T Deluxe
- Memory
- 12Gb Corsair XMS DDR3 PC3-12800 (1600) CAS 9
- Graphics Card(s)
- 768Mb Nvidia Quadro FX 1800
- Sound Card
- onboard
- Monitor(s) Displays
- Apple Cinema (aluminium) 20"
- Screen Resolution
- 1680 x 1050
- Hard Drives
- 160 Gb Intel SSD Gen 2
- PSU
- 550W Corsair
- Case
- Lian Li
- Cooling
- Noctua NH-U12P SE2 Dual Fan
- Other Info
- 3 x 1TB WD Caviar Black storage drives.