Not sure what to think of this. I would assume that vista would be able to
seamlessly handle both ipv4 and ipv6 addresses. I have windows vista ultimate
x64 running, and I am attempting to do file/samba sharing with it. I can
access it fine with my laptop through my private network with my Vista Laptop
(Ultimate x86), but I am unable to access the share with another XP machine
(XP Home). What's interesting, is when I ping the machine name from my vista
laptop to it, the name gets resolved to ipv6, and it receives responses.
However, when I use the same machine to ping it using it's ipv4 address, it
receives no responses.

I figure this might be the problem, but the XP machine also has ipv6
installed, and is still not able to resolve the address.

I did install LLTD on the XP machine, so the vista x64 desktop does show up
in the workgroup explorer, but it is not able to connect to it at all. I
figure that it must have something to do with XP unable to resolve computer
names to ipv6??

In any case, it would be nice to still be able to access my vista desktop
with a regular ipv4 address - it's a whole lot easier to remember


Any suggestions or ideas are happily taken, as this problem has been killing
me.

Thanks!

Danny

I forgot to mention that I have tried disabling (unchecking) ipv6 on the nic
properties to no avail as well.

"dcb" wrote:

Not sure what to think of this. I would assume that vista would be able to
seamlessly handle both ipv4 and ipv6 addresses. I have windows vista ultimate
x64 running, and I am attempting to do file/samba sharing with it. I can
access it fine with my laptop through my private network with my Vista Laptop
(Ultimate x86), but I am unable to access the share with another XP machine
(XP Home). What's interesting, is when I ping the machine name from my vista
laptop to it, the name gets resolved to ipv6, and it receives responses.
However, when I use the same machine to ping it using it's ipv4 address, it
receives no responses.

I figure this might be the problem, but the XP machine also has ipv6
installed, and is still not able to resolve the address.

I did install LLTD on the XP machine, so the vista x64 desktop does show up
in the workgroup explorer, but it is not able to connect to it at all. I
figure that it must have something to do with XP unable to resolve computer
names to ipv6??

In any case, it would be nice to still be able to access my vista desktop
with a regular ipv4 address - it's a whole lot easier to remember


Any suggestions or ideas are happily taken, as this problem has been killing
me.

Thanks!

Danny

Posting the the results of both XP and Vista x64 ipconfig /all here may
help.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


"dcb" wrote in message
...
Not sure what to think of this. I would assume that vista would be able to
seamlessly handle both ipv4 and ipv6 addresses. I have windows vista
ultimate
x64 running, and I am attempting to do file/samba sharing with it. I can
access it fine with my laptop through my private network with my Vista
Laptop
(Ultimate x86), but I am unable to access the share with another XP
machine
(XP Home). What's interesting, is when I ping the machine name from my
vista
laptop to it, the name gets resolved to ipv6, and it receives responses.
However, when I use the same machine to ping it using it's ipv4 address,
it
receives no responses.

I figure this might be the problem, but the XP machine also has ipv6
installed, and is still not able to resolve the address.

I did install LLTD on the XP machine, so the vista x64 desktop does show
up
in the workgroup explorer, but it is not able to connect to it at all. I
figure that it must have something to do with XP unable to resolve
computer
names to ipv6??

In any case, it would be nice to still be able to access my vista desktop
with a regular ipv4 address - it's a whole lot easier to remember


Any suggestions or ideas are happily taken, as this problem has been
killing
me.

Thanks!

Danny

Heres the ouput:



The vista x64 Desktop:

Windows IP Configuration

Host Name . . . . . . . . . . . . : XXXXXXX
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-EA-19-99-88-77
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b4ab:a64a:51e0:8e5e%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.103(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.128
Lease Obtained. . . . . . . . . . : Sunday, January 06, 2008 10:07:15 AM
Lease Expires . . . . . . . . . . : Tuesday, January 08, 2008 1:19:38 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 201333756
DNS Servers . . . . . . . . . . . : 204.127.203.135
216.148.225.135
NetBIOS over Tcpip. . . . . . . . : Enabled




The Windows XP Laptop:


Windows IP Configuration

Host Name . . . . . . . . . . . . : XXXXXXX
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No


Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG
Network Connection
Physical Address. . . . . . . . . : 00-0F-35-AD-22-AC
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.128
IP Address. . . . . . . . . . . . : fe80::20e:35ff:feaf:12ac%5
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 204.127.203.135
216.148.225.135
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Lease Obtained. . . . . . . . . . : Sunday, January 06, 2008
11:44:20 PM

Lease Expires . . . . . . . . . . : Monday, January 07, 2008
11:44:20 PM



"Robert L. (MS-MVP)" wrote:

Posting the the results of both XP and Vista x64 ipconfig /all here may
help.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


"dcb" wrote in message
...
Not sure what to think of this. I would assume that vista would be able to
seamlessly handle both ipv4 and ipv6 addresses. I have windows vista
ultimate
x64 running, and I am attempting to do file/samba sharing with it. I can
access it fine with my laptop through my private network with my Vista
Laptop
(Ultimate x86), but I am unable to access the share with another XP
machine
(XP Home). What's interesting, is when I ping the machine name from my
vista
laptop to it, the name gets resolved to ipv6, and it receives responses.
However, when I use the same machine to ping it using it's ipv4 address,
it
receives no responses.

I figure this might be the problem, but the XP machine also has ipv6
installed, and is still not able to resolve the address.

I did install LLTD on the XP machine, so the vista x64 desktop does show
up
in the workgroup explorer, but it is not able to connect to it at all. I
figure that it must have something to do with XP unable to resolve
computer
names to ipv6??

In any case, it would be nice to still be able to access my vista desktop
with a regular ipv4 address - it's a whole lot easier to remember


Any suggestions or ideas are happily taken, as this problem has been
killing
me.

Thanks!

Danny

XP doesn't show NetBIOS over TCP/IP.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


"dcb" wrote in message
...
Heres the ouput:



The vista x64 Desktop:

Windows IP Configuration

Host Name . . . . . . . . . . . . : XXXXXXX
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-EA-19-99-88-77
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::b4ab:a64a:51e0:8e5e%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.103(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.128
Lease Obtained. . . . . . . . . . : Sunday, January 06, 2008 10:07:15 AM
Lease Expires . . . . . . . . . . : Tuesday, January 08, 2008 1:19:38 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 201333756
DNS Servers . . . . . . . . . . . : 204.127.203.135
216.148.225.135
NetBIOS over Tcpip. . . . . . . . : Enabled




The Windows XP Laptop:


Windows IP Configuration

Host Name . . . . . . . . . . . . : XXXXXXX
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No


Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG
Network Connection
Physical Address. . . . . . . . . : 00-0F-35-AD-22-AC
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.128
IP Address. . . . . . . . . . . . : fe80::20e:35ff:feaf:12ac%5
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 204.127.203.135
216.148.225.135
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Lease Obtained. . . . . . . . . . : Sunday, January 06, 2008
11:44:20 PM

Lease Expires . . . . . . . . . . : Monday, January 07, 2008
11:44:20 PM



"Robert L. (MS-MVP)" wrote:

Posting the the results of both XP and Vista x64 ipconfig /all here may
help.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


"dcb" wrote in message
...
Not sure what to think of this. I would assume that vista would be able
to
seamlessly handle both ipv4 and ipv6 addresses. I have windows vista
ultimate
x64 running, and I am attempting to do file/samba sharing with it. I
can
access it fine with my laptop through my private network with my Vista
Laptop
(Ultimate x86), but I am unable to access the share with another XP
machine
(XP Home). What's interesting, is when I ping the machine name from my
vista
laptop to it, the name gets resolved to ipv6, and it receives
responses.
However, when I use the same machine to ping it using it's ipv4
address,
it
receives no responses.

I figure this might be the problem, but the XP machine also has ipv6
installed, and is still not able to resolve the address.

I did install LLTD on the XP machine, so the vista x64 desktop does
show
up
in the workgroup explorer, but it is not able to connect to it at all.
I
figure that it must have something to do with XP unable to resolve
computer
names to ipv6??

In any case, it would be nice to still be able to access my vista
desktop
with a regular ipv4 address - it's a whole lot easier to remember


Any suggestions or ideas are happily taken, as this problem has been
killing
me.

Thanks!

Danny