I have Vista x64 and I have read threads on this for weeks and can't fix
it. I have file sharing/network discovery on, private network, password
protection disabled, my shares set to everyone and everyone is on the
same workgroup.

My problem is that the x64 Vista computer will not see any of the XP
(x86 or x64) computers and they can't see it from the Network
Neighbourhood. However, if I type the IP address of the XP computers I
can access them. On the XP computers if I type the IP address I get an
error that it isn't accessable and I might not have permission.
However, if I type \\192.168.0.100\share or any of the other share names
I access it just fine. pinging works too by IP but not by name. If I
boot into the x86 install of have of Vista I can access XP computers
from Vista and the Vista from XP by name and everything without typing
any user names. The only differince between the two aside from x64 and
x86 is that x86 isn't patched past SP1 as I don't use it often.

Lastly after installing that XP patch I can see the x86 XP computers by
name from the network map feature on Vista, still can't access them by
name though...

Any ideas?


--
DarExc

Sounds like a firewall issue to me. Are you running any VPN clients? I
had a similar issue with the firewall built into Checkpoint's VPN
client. If not using VPN, you might also want to check that the Windows
Firewall settings and LAN configuration on the Vista box are the same
under x86 and x64 (especially check to see if the netBIOS over tcpip
setting is enabled on x86).


--
mkprilliman

"The Deathstar is fully operational."

Antec Nine Hundred / Core 2 Quad Q6600 / MSI P6N Diamond / CoolerMaster
RP Pro 1000 PSU / X-Fi 7.1 / 4x 1GB Corsair XMS2 PC-6400 / 2x MSI
NX8600GTS-OC / 150GB Raptor (system) / 4 x 500GB HDD (RAID 5) / 1x 300GB
HDD (beta partition) / Venus T4U (1TB capacity) / 1x Dell 2407WFP
wrapped by 2x 20.1" FPs/ Logitech Z-5300 speakers

Thanks for the quick reply. I'm using NOD32 with no extra firewall
other than windows one. I looked through again and every exception for
sharing is there. Even if I disable the firewall all together still
have the problem. Netbois is set to automatic on both, enabled or
disabled same result though. No VPN at all.


--
DarExc

Hmmm, still sounds like a name resolution issue.

How about trying a simple test?
On the Vista machine open up a command window (Run-cmd), and issue the
following command at the prompt:
net use \\theIPAddressForXPMachine
(i.e. net use \\192.168.0.100)

Then try the same command using the name of the same XP machine:
i.e.
net use \\XpMachineName

(These are examples from my PC and reflect what you would want to see
here if everything was working):
C:\Users\Mikenet use \\192.168.1.20
The command completed successfully.

C:\Users\Mikenet use \\deathstar
The command completed successfully.

My guess is that your first command using i.p. will work, but the
second attempt using machine name will fail and return something like
"System error xx has occurred."

Please post back with any error codes you receive.


--
mkprilliman

"The Deathstar is fully operational."

Antec Nine Hundred / Core 2 Quad Q6600 / MSI P6N Diamond / CoolerMaster
RP Pro 1000 PSU / X-Fi 7.1 / 4x 1GB Corsair XMS2 PC-6400 / 2x MSI
NX8600GTS-OC / 150GB Raptor (system) / 4 x 500GB HDD (RAID 5) / 1x 300GB
HDD (beta partition) / Venus T4U (1TB capacity) / 1x Dell 2407WFP
wrapped by 2x 20.1" FPs/ Logitech Z-5300 speakers

On Tue, 6 May 2008 16:09:25 -0500, DarExc wrote:


Thanks for the quick reply. I'm using NOD32 with no extra firewall
other than windows one. I looked through again and every exception for
sharing is there. Even if I disable the firewall all together still
have the problem. Netbois is set to automatic on both, enabled or
disabled same result though. No VPN at all.

Check NOD32 instructions, and look for anti-worm protection. AW will block
SMBs, just like a firewall. Disabling NOD32 won't disable the anti-worm
component.
http://networking.nitecruzr.net/2006/07/advanced-windows-networking-using.html
http://networking.nitecruzr.net/2006...ing-using.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://networking.nitecruzr.net/

All these computers ARE on the same workgroup. eg mshome or workgroup etc

Try downgrading the Authentication level of the Vista LAN Manager as an
experiment

Start / Control Panel / Administrative tools / Local Security Policy / Local
Policies / Security Options /

Network security: LAN manager authentication level. Change this to Send LM &
NTLM - use NTLMv2 session security if negotiated

If it makes no difference set it back again.

Dave


"mkprilliman" wrote in message
...

Hmmm, still sounds like a name resolution issue.

How about trying a simple test?
On the Vista machine open up a command window (Run-cmd), and issue the
following command at the prompt:
net use \\theIPAddressForXPMachine
(i.e. net use \\192.168.0.100)

Then try the same command using the name of the same XP machine:
i.e.
net use \\XpMachineName

(These are examples from my PC and reflect what you would want to see
here if everything was working):
C:\Users\Mikenet use \\192.168.1.20
The command completed successfully.

C:\Users\Mikenet use \\deathstar
The command completed successfully.

My guess is that your first command using i.p. will work, but the
second attempt using machine name will fail and return something like
"System error xx has occurred."

Please post back with any error codes you receive.


--
mkprilliman

"The Deathstar is fully operational."

Antec Nine Hundred / Core 2 Quad Q6600 / MSI P6N Diamond / CoolerMaster
RP Pro 1000 PSU / X-Fi 7.1 / 4x 1GB Corsair XMS2 PC-6400 / 2x MSI
NX8600GTS-OC / 150GB Raptor (system) / 4 x 500GB HDD (RAID 5) / 1x 300GB
HDD (beta partition) / Venus T4U (1TB capacity) / 1x Dell 2407WFP
wrapped by 2x 20.1" FPs/ Logitech Z-5300 speakers

Read the bottom part about XP's home and small business wizaed to set up file
sharing

http://technet.microsoft.com/en-us/l.../bb727037.aspx

Have a read of the above link re Vista File and Printer Sharing.

Permissions/Share info is there as well.

If using Norton, McAfee, Trend Micro I.S., make sure file and printer
sharing is enabled in THEIR firewall .(LAN allowed)

1st thing to do is make sure that the Workgroup Name of ALL the computers is
the SAME.

In Vista Network and Sharing:

Network Discovery: ON (So it can see the other computers)

Network set to Private (Public is for hotspots, airports, etc)

File Sharing: ON

Public Folder Sharing: ON (Vista’s Public Folder is the same as XP’s Shared
Docs)

Password Protected: OFF (unless you want to set up identical usernames, and
passwords (they can be different) on ALL computers in your Network). If you
have it ON, you will be asked for a username and password when you try to
access a Vista computer from an XP computer, or a Vista Computer.

Also, If you haven’t done so already, run XP’s Network Setup Wizard (in
Start All Programs Accessories Communications), and tell the Wizard to
enable File and Printer Sharing.
Or Start Control Panel Network Connections Set up a Home or Small
Office Network.

--
Mick Murphy - Qld - Australia


"Dave Griffiths" wrote:

All these computers ARE on the same workgroup. eg mshome or workgroup etc

Try downgrading the Authentication level of the Vista LAN Manager as an
experiment

Start / Control Panel / Administrative tools / Local Security Policy / Local
Policies / Security Options /

Network security: LAN manager authentication level. Change this to Send LM &
NTLM - use NTLMv2 session security if negotiated

If it makes no difference set it back again.

Dave


"mkprilliman" wrote in message
...

Hmmm, still sounds like a name resolution issue.

How about trying a simple test?
On the Vista machine open up a command window (Run-cmd), and issue the
following command at the prompt:
net use \\theIPAddressForXPMachine
(i.e. net use \\192.168.0.100)

Then try the same command using the name of the same XP machine:
i.e.
net use \\XpMachineName

(These are examples from my PC and reflect what you would want to see
here if everything was working):
C:\Users\Mikenet use \\192.168.1.20
The command completed successfully.

C:\Users\Mikenet use \\deathstar
The command completed successfully.

My guess is that your first command using i.p. will work, but the
second attempt using machine name will fail and return something like
"System error xx has occurred."

Please post back with any error codes you receive.


--
mkprilliman

"The Deathstar is fully operational."

Antec Nine Hundred / Core 2 Quad Q6600 / MSI P6N Diamond / CoolerMaster
RP Pro 1000 PSU / X-Fi 7.1 / 4x 1GB Corsair XMS2 PC-6400 / 2x MSI
NX8600GTS-OC / 150GB Raptor (system) / 4 x 500GB HDD (RAID 5) / 1x 300GB
HDD (beta partition) / Venus T4U (1TB capacity) / 1x Dell 2407WFP
wrapped by 2x 20.1" FPs/ Logitech Z-5300 speakers

Wow, thanks for all the advice, I got a chance to try it all tonight,

mkprilliman, you are right, by IP it works and by name it says error 53
network path not found

Dave, it seem to make no difference with the network security.

Mick thanks but all those settings are already in place.

Chuck, I disabled the IMON anti worm protection as well with no luck.
I did however, notice my NetBIOS over TCP/IP was not set to enabled but
rather default. I set it to enabled on the Vista computer and my x86 XP
Laptop and the Vista one is still showing it as disabled. The help
through a link on the link you posted though doesn't seem to help me
out. Could this be my problem?

Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E
Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 00-1D-60-71-53-C6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::d425:88ff:41f9:7184%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : May 9, 2008 11:13:04 PM
Lease Expires . . . . . . . . . . : June 16, 2144 9:22:09 AM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Disabled


--
DarExc

On Sat, 10 May 2008 02:06:11 -0500, DarExc wrote:


Wow, thanks for all the advice, I got a chance to try it all tonight,

mkprilliman, you are right, by IP it works and by name it says error 53
network path not found

Dave, it seem to make no difference with the network security.

Mick thanks but all those settings are already in place.

Chuck, I disabled the IMON anti worm protection as well with no luck.
I did however, notice my NetBIOS over TCP/IP was not set to enabled but
rather default. I set it to enabled on the Vista computer and my x86 XP
Laptop and the Vista one is still showing it as disabled. The help
through a link on the link you posted though doesn't seem to help me
out. Could this be my problem?

Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E
Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 00-1D-60-71-53-C6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::d425:88ff:41f9:7184%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : May 9, 2008 11:13:04 PM
Lease Expires . . . . . . . . . . : June 16, 2144 9:22:09 AM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Disabled

I'm still learning to read IPConfig logs from Vista, because they include detail
for both IPV4 and IPV6. Maybe if you include the entire log, not an excerpt, we
can parse it more reliably. The "NetBT Disabled" does look relevant though.

Your problem starts with Server Message Block interference.
"the x64 Vista computer will not see any of the XP (x86 or x64) computers and
they can't see it from the Network Neighbourhood."
That's a browser issue, and the browser uses SMBs (generally over NetBIOS Over
TCP/IP but sometimes directly over IP).

Start by reading about the NT browser (which is what provides the display in
Network Neighborhood - or Network).
http://networking.nitecruzr.net/2005/04/nt-browser-or-why-cant-i-always-see.html
http://networking.nitecruzr.net/2005...lways-see.html

Then, go back and re read about SMBs over NetBT, vs SMBs directly hosted over
IP.
http://networking.nitecruzr.net/2006/07/advanced-windows-networking-using.html
http://networking.nitecruzr.net/2006...ing-using.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://networking.nitecruzr.net/

DarExc;707800 Wrote:
Wow, thanks for all the advice, I got a chance to try it all tonight,

mkprilliman, you are right, by IP it works and by name it says error 53
network path not found

Dave, it seem to make no difference with the network security.

Mick thanks but all those settings are already in place.

Chuck, I disabled the IMON anti worm protection as well with no luck. I
did however, notice my NetBIOS over TCP/IP was not set to enabled but
rather default. I set it to enabled on the Vista computer and my x86 XP
Laptop and the Vista one is still showing it as disabled. The help
through a link on the link you posted though doesn't seem to help me
out. Could this be my problem?

Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit
Ethernet Controller
Physical Address. . . . . . . . . : 00-1D-60-71-53-C6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::d425:88ff:41f9:7184%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : May 9, 2008 11:13:04 PM
Lease Expires . . . . . . . . . . : June 16, 2144 9:22:09 AM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Disabled
OK, that is what I might have anticipated. You might want to take a
look at the following description of sys error 53 (gleaned from
'Networking, VPN, TS, Remote Access and Internet Troubleshooting'
(http://chicagotech.net)):


*System error 53 - The network path was not found.*
Symptom: when using net view '_\\ip_' (file://ip/) or
'_\\computername_' (file://computername/), you get system error 53.
Resolutions:1) if it is domain environment, check your WINS; 2) if it
is peer-to-peer workgroup, enable NetBIOS over TCP/IP; 3) make sure the
machine is running; 4) make sure file and Printer Share enabled on
remote computer; 5) make sure client for ms networks is enabled on local
computer; 6) make sure you type the correct name. 7) Make sure no
firewall running or any security setting.
VPN Case Study -
*'_Can_ping_VPN_server_but_receive_System_error_53 _using_net_use_'
(http://www.chicagotech.net/VPN/vpn&firewall.htm)*
Case Study *- **'_System_Error_53_-_The_network_path_was_not_found._'
(http://www.chicagotech.net/troublesh...merror53.htm)*


--
mkprilliman

"The Deathstar is fully operational."

Antec Nine Hundred / Core 2 Quad Q6600 / MSI P6N Diamond / CoolerMaster
RP Pro 1000 PSU / X-Fi 7.1 / 4x 1GB Corsair XMS2 PC-6400 / 2x MSI
NX8600GTS-OC / 150GB Raptor (system) / 4 x 500GB HDD (RAID 5) / 1x 300GB
HDD (beta partition) / Venus T4U (1TB capacity) / 1x Dell 2407WFP
wrapped by 2x 20.1" FPs/ Logitech Z-5300 speakers