I have a Windows XP Client running on a Windows 7/64 host, it's been running fine for a while. It has password access to 3 shared drives on the host via the local network. After it boots I click on one of the drives in My Computer and enter the password. It also a folder on the virtual C drive that is marked as shared (with no password). As of yesterday when I click on a network drive (to enter the password) there is a 10 second delay and a message .... The network path was not found .... - so I cannot run any XP apps that needs that data. Otherwise XP looks like its working.
From the Windows 7 host if I access Network- I can see the XP virtual machine and access its shared C: folder, so there is connectivity. If I click the Windows 7 machine within Network I see its shared drives.
If I click on Network and Sharing Center I see two Items
1. Network/Home Network - joined
2. Unidentified Network / Public Network / No Network Access / Connections: [several] e.g VirtualaBox Host Only Network/ VMware Network Adapter with a connection time equal to the time the host machine has been booted up
XP Client can no longer access network drives
-
AnrDaemon
- Posts: 134
- Joined: 7. Feb 2010, 23:41
- Primary OS: MS Windows 7
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Ubuntu Linux, Windows
Re: XP Client can no longer access network drives
What is the output of
from the host?
Also, can you
from the guest?
Code: Select all
net shareAlso, can you
Code: Select all
telnet host_ip 139Re: XP Client can no longer access network drives
net share
-guest-----------------------------------------
jooopty C:\Documents and Settings\xxxxxx\My Documents <<< this is the XP C: shared directory
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS
--host----------------------------------------- note I have a lot of drives - C-K,Z internal drive & PQR external drives
D F G shared drives / NV & clarion6 shared folders
Share name Resource Remark
ADMIN$ C:\Windows Remote Admin
C$ C:\ Default share
R$ R:\ Default share
Q$ Q:\ Default share
print$ C:\Windows\system32\spool\drivers
Printer Drivers
D$ D:\ Default share
E$ E:\ Default share
P$ P:\ Default share
F$ F:\ Default share
M$ M:\ Default share
G$ G:\ Default share
H$ H:\ Default share
L$ L:\ Default share
I$ I:\ Default share
IPC$ Remote IPC
J$ J:\ Default share
K$ K:\ Default share
Z$ Z:\ Default share
clarion6 G:\clarion6
D D:\
F F:\
G G:\
NV D:\NV
Users C:\Users
Canon MF4100 Series UFRII LT
LPT1: Spooled Canon MF4100 Series UFRII LT
HP LaserJet 4 Plus
USB001 Spooled HP LaserJet 4 Plus
-----------------------------------------------------------------------------------------
telnet host_ip 139 -- from the guest?
could not open connect to the host on port 139
-guest-----------------------------------------
jooopty C:\Documents and Settings\xxxxxx\My Documents <<< this is the XP C: shared directory
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS
--host----------------------------------------- note I have a lot of drives - C-K,Z internal drive & PQR external drives
D F G shared drives / NV & clarion6 shared folders
Share name Resource Remark
ADMIN$ C:\Windows Remote Admin
C$ C:\ Default share
R$ R:\ Default share
Q$ Q:\ Default share
print$ C:\Windows\system32\spool\drivers
Printer Drivers
D$ D:\ Default share
E$ E:\ Default share
P$ P:\ Default share
F$ F:\ Default share
M$ M:\ Default share
G$ G:\ Default share
H$ H:\ Default share
L$ L:\ Default share
I$ I:\ Default share
IPC$ Remote IPC
J$ J:\ Default share
K$ K:\ Default share
Z$ Z:\ Default share
clarion6 G:\clarion6
D D:\
F F:\
G G:\
NV D:\NV
Users C:\Users
Canon MF4100 Series UFRII LT
LPT1: Spooled Canon MF4100 Series UFRII LT
HP LaserJet 4 Plus
USB001 Spooled HP LaserJet 4 Plus
-----------------------------------------------------------------------------------------
telnet host_ip 139 -- from the guest?
could not open connect to the host on port 139
Re: XP Client can no longer access network drives
As an experiment - I just modified the setup to add a different host shared folder within the VM settings - not as a network share. It does not even show up when I boot XP.
Re: XP Client can no longer access network drives
Several hours of searching for solutions and playing around yielded nothing. Then I had an inspired guess. It appears to be Norton Internet Security:
Smart Firewall -> Trust Control -> Local Area Connection -
select the VM/XP Computer and change to Full Trust from Network Trust Shared
At this point the drives become accessable without an XP reboot.
I'm assuming a Norton update changed something slightly.
I've turned Full Trust off and it keeps working, but I'm guessing when the host reboots it will fail again.
Smart Firewall -> Trust Control -> Local Area Connection -
select the VM/XP Computer and change to Full Trust from Network Trust Shared
At this point the drives become accessable without an XP reboot.
I'm assuming a Norton update changed something slightly.
I've turned Full Trust off and it keeps working, but I'm guessing when the host reboots it will fail again.
-
AnrDaemon
- Posts: 134
- Joined: 7. Feb 2010, 23:41
- Primary OS: MS Windows 7
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Ubuntu Linux, Windows
Re: XP Client can no longer access network drives
[1]Bob R wrote:telnet host_ip 139 -- from the guest?
could not open connect to the host on port 139
Judging from [1], this was rather apparent. (139/tcp is a Server Message Blocks protocol port, which is (nowadays) used as a fallback), but still worth the diagnostic purposes.Bob R wrote:Several hours of searching for solutions and playing around yielded nothing. Then I had an inspired guess. It appears to be Norton Internet Security:
Re: XP Client can no longer access network drives
What makes no sense is that I changed Norton back to the original [more conservative] firewall setting, rebooted the host and the VM/XP and it still works.
Thanks very much for your help.
Thanks very much for your help.
-
AnrDaemon
- Posts: 134
- Joined: 7. Feb 2010, 23:41
- Primary OS: MS Windows 7
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Ubuntu Linux, Windows
Re: XP Client can no longer access network drives
On my memory, NIS never made any sense. Back from year 1995...