I had no trouble connecting my laptop to my wireless router for internet 
access, but I cannot connect to my home network properly. I installed the 
LLTD Responder on the XP machines, and I can see them on the network map, but 
I cannot access their shared files, nor can I see them when I view the actual 
network. The Vista machines workgroup has the same name as the XP ones. BTW 
the XP machines can't seem to find the laptop either.

Have a read of info below, especially XP's file sharing Network wizard.

http://technet.microsoft.com/en-us/library/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 (or LAN allowed, depending on how their 
Exceptions are worded in their Firewall)

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 (passwords 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, run the XP’s Home or Small Office Network File and Printer Sharing 
Wizard to include Vista in your “New” Network, even if you had an XP Network 
set up prior to adding a Vista computer to it(redoing the Wizard seems to 
work for XP machines!). 

In “My Network Places”: “Set up a Home or Small Office Network”
OR under Accessories > Communications > Network Setup Wizard > Allow File 
and Printer Sharing.

-- 
Mick Murphy - Qld - Australia


"CJ" wrote:

> I had no trouble connecting my laptop to my wireless router for internet 
> access, but I cannot connect to my home network properly. I installed the 
> LLTD Responder on the XP machines, and I can see them on the network map, but 
> I cannot access their shared files, nor can I see them when I view the actual 
> network. The Vista machines workgroup has the same name as the XP ones. BTW 
> the XP machines can't seem to find the laptop either.

I first messed with the Norton Firewall settings (which were really weird, 
because they had a "block windows file sharing" and an "allow windows file 
sharing" checkboxes and both were selected. :S) 

Then I tried to turn off password protection on the vista machine, but it 
kept on alerting me with "the parameter is incorrect." 

I ran the network setup wizard on one of the machines, but it didn't change 
anything. 

I tried plugging into the router because the vista laptop was connecting 
wirelessly and the XP desktops were wired. I ran the windows XP Network setup 
on the XP machines, but they still didn't detect the laptop even after I 
tried running the network setup disk on the laptop.

This is driving me nuts! I can't figure out what's wrong here.

"Mick Murphy" wrote:

> Have a read of info below, especially XP's file sharing Network wizard.
> 
> http://technet.microsoft.com/en-us/library/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 (or LAN allowed, depending on how their 
> Exceptions are worded in their Firewall)
> 
> 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 (passwords 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, run the XP’s Home or Small Office Network File and Printer Sharing 
> Wizard to include Vista in your “New” Network, even if you had an XP Network 
> set up prior to adding a Vista computer to it(redoing the Wizard seems to 
> work for XP machines!). 
> 
> In “My Network Places”: “Set up a Home or Small Office Network”
> OR under Accessories > Communications > Network Setup Wizard > Allow File 
> and Printer Sharing.
> 
> -- 
> Mick Murphy - Qld - Australia
> 
> 
> "CJ" wrote:
> 
> > I had no trouble connecting my laptop to my wireless router for internet 
> > access, but I cannot connect to my home network properly. I installed the 
> > LLTD Responder on the XP machines, and I can see them on the network map, but 
> > I cannot access their shared files, nor can I see them when I view the actual 
> > network. The Vista machines workgroup has the same name as the XP ones. BTW 
> > the XP machines can't seem to find the laptop either.

Nowhere have I said to run the XP setup wizard on the Vista Laptop!
Why would you!
-- 
Mick Murphy - Qld - Australia


"CJ" wrote:

> I first messed with the Norton Firewall settings (which were really weird, 
> because they had a "block windows file sharing" and an "allow windows file 
> sharing" checkboxes and both were selected. :S) 
> 
> Then I tried to turn off password protection on the vista machine, but it 
> kept on alerting me with "the parameter is incorrect." 
> 
> I ran the network setup wizard on one of the machines, but it didn't change 
> anything. 
> 
> I tried plugging into the router because the vista laptop was connecting 
> wirelessly and the XP desktops were wired. I ran the windows XP Network setup 
> on the XP machines, but they still didn't detect the laptop even after I 
> tried running the network setup disk on the laptop.
> 
> This is driving me nuts! I can't figure out what's wrong here.
> 
> "Mick Murphy" wrote:
> 
> > Have a read of info below, especially XP's file sharing Network wizard.
> > 
> > http://technet.microsoft.com/en-us/library/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 (or LAN allowed, depending on how their 
> > Exceptions are worded in their Firewall)
> > 
> > 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 (passwords 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, run the XP’s Home or Small Office Network File and Printer Sharing 
> > Wizard to include Vista in your “New” Network, even if you had an XP Network 
> > set up prior to adding a Vista computer to it(redoing the Wizard seems to 
> > work for XP machines!). 
> > 
> > In “My Network Places”: “Set up a Home or Small Office Network”
> > OR under Accessories > Communications > Network Setup Wizard > Allow File 
> > and Printer Sharing.
> > 
> > -- 
> > Mick Murphy - Qld - Australia
> > 
> > 
> > "CJ" wrote:
> > 
> > > I had no trouble connecting my laptop to my wireless router for internet 
> > > access, but I cannot connect to my home network properly. I installed the 
> > > LLTD Responder on the XP machines, and I can see them on the network map, but 
> > > I cannot access their shared files, nor can I see them when I view the actual 
> > > network. The Vista machines workgroup has the same name as the XP ones. BTW 
> > > the XP machines can't seem to find the laptop either.

Good question. It's never worked; I just ran it because nothing else was 
working. BTW the "parameter is incorrect" message stopped coming up after I 
restarted my computer. So all the settings on the vista laptop are correct 
now. The network still isn't working.

Is it an issue if the network map shows the laptop connected to the router 
and the desktops to a "switch" that is connected to the router?

"Mick Murphy" wrote:

> Nowhere have I said to run the XP setup wizard on the Vista Laptop!
> Why would you!
> -- 
> Mick Murphy - Qld - Australia
> 
> 
> "CJ" wrote:
> 
> > I first messed with the Norton Firewall settings (which were really weird, 
> > because they had a "block windows file sharing" and an "allow windows file 
> > sharing" checkboxes and both were selected. :S) 
> > 
> > Then I tried to turn off password protection on the vista machine, but it 
> > kept on alerting me with "the parameter is incorrect." 
> > 
> > I ran the network setup wizard on one of the machines, but it didn't change 
> > anything. 
> > 
> > I tried plugging into the router because the vista laptop was connecting 
> > wirelessly and the XP desktops were wired. I ran the windows XP Network setup 
> > on the XP machines, but they still didn't detect the laptop even after I 
> > tried running the network setup disk on the laptop.
> > 
> > This is driving me nuts! I can't figure out what's wrong here.
> > 
> > "Mick Murphy" wrote:
> > 
> > > Have a read of info below, especially XP's file sharing Network wizard.
> > > 
> > > http://technet.microsoft.com/en-us/library/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 (or LAN allowed, depending on how their 
> > > Exceptions are worded in their Firewall)
> > > 
> > > 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 (passwords 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, run the XP’s Home or Small Office Network File and Printer Sharing 
> > > Wizard to include Vista in your “New” Network, even if you had an XP Network 
> > > set up prior to adding a Vista computer to it(redoing the Wizard seems to 
> > > work for XP machines!). 
> > > 
> > > In “My Network Places”: “Set up a Home or Small Office Network”
> > > OR under Accessories > Communications > Network Setup Wizard > Allow File 
> > > and Printer Sharing.
> > > 
> > > -- 
> > > Mick Murphy - Qld - Australia
> > > 
> > > 
> > > "CJ" wrote:
> > > 
> > > > I had no trouble connecting my laptop to my wireless router for internet 
> > > > access, but I cannot connect to my home network properly. I installed the 
> > > > LLTD Responder on the XP machines, and I can see them on the network map, but 
> > > > I cannot access their shared files, nor can I see them when I view the actual 
> > > > network. The Vista machines workgroup has the same name as the XP ones. BTW 
> > > > the XP machines can't seem to find the laptop either.

OK, so I have no idea how this happened, but now my computer's connected to 
the network! Thanks for all your help!

"CJ" wrote:

> Good question. It's never worked; I just ran it because nothing else was 
> working. BTW the "parameter is incorrect" message stopped coming up after I 
> restarted my computer. So all the settings on the vista laptop are correct 
> now. The network still isn't working.
> 
> Is it an issue if the network map shows the laptop connected to the router 
> and the desktops to a "switch" that is connected to the router?
> 
> "Mick Murphy" wrote:
> 
> > Nowhere have I said to run the XP setup wizard on the Vista Laptop!
> > Why would you!
> > -- 
> > Mick Murphy - Qld - Australia
> > 
> > 
> > "CJ" wrote:
> > 
> > > I first messed with the Norton Firewall settings (which were really weird, 
> > > because they had a "block windows file sharing" and an "allow windows file 
> > > sharing" checkboxes and both were selected. :S) 
> > > 
> > > Then I tried to turn off password protection on the vista machine, but it 
> > > kept on alerting me with "the parameter is incorrect." 
> > > 
> > > I ran the network setup wizard on one of the machines, but it didn't change 
> > > anything. 
> > > 
> > > I tried plugging into the router because the vista laptop was connecting 
> > > wirelessly and the XP desktops were wired. I ran the windows XP Network setup 
> > > on the XP machines, but they still didn't detect the laptop even after I 
> > > tried running the network setup disk on the laptop.
> > > 
> > > This is driving me nuts! I can't figure out what's wrong here.
> > > 
> > > "Mick Murphy" wrote:
> > > 
> > > > Have a read of info below, especially XP's file sharing Network wizard.
> > > > 
> > > > http://technet.microsoft.com/en-us/library/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 (or LAN allowed, depending on how their 
> > > > Exceptions are worded in their Firewall)
> > > > 
> > > > 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 (passwords 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, run the XP’s Home or Small Office Network File and Printer Sharing 
> > > > Wizard to include Vista in your “New” Network, even if you had an XP Network 
> > > > set up prior to adding a Vista computer to it(redoing the Wizard seems to 
> > > > work for XP machines!). 
> > > > 
> > > > In “My Network Places”: “Set up a Home or Small Office Network”
> > > > OR under Accessories > Communications > Network Setup Wizard > Allow File 
> > > > and Printer Sharing.
> > > > 
> > > > -- 
> > > > Mick Murphy - Qld - Australia
> > > > 
> > > > 
> > > > "CJ" wrote:
> > > > 
> > > > > I had no trouble connecting my laptop to my wireless router for internet 
> > > > > access, but I cannot connect to my home network properly. I installed the 
> > > > > LLTD Responder on the XP machines, and I can see them on the network map, but 
> > > > > I cannot access their shared files, nor can I see them when I view the actual 
> > > > > network. The Vista machines workgroup has the same name as the XP ones. BTW 
> > > > > the XP machines can't seem to find the laptop either.

This one will remain one of life's littler mysteries!
In networking, when you set it up, you have to reboot for the settings to 
"be set in concrete".
However you got there, I'm glad you did!
-- 
Mick Murphy - Qld - Australia


"CJ" wrote:

> OK, so I have no idea how this happened, but now my computer's connected to 
> the network! Thanks for all your help!
> 
> "CJ" wrote:
> 
> > Good question. It's never worked; I just ran it because nothing else was 
> > working. BTW the "parameter is incorrect" message stopped coming up after I 
> > restarted my computer. So all the settings on the vista laptop are correct 
> > now. The network still isn't working.
> > 
> > Is it an issue if the network map shows the laptop connected to the router 
> > and the desktops to a "switch" that is connected to the router?
> > 
> > "Mick Murphy" wrote:
> > 
> > > Nowhere have I said to run the XP setup wizard on the Vista Laptop!
> > > Why would you!
> > > -- 
> > > Mick Murphy - Qld - Australia
> > > 
> > > 
> > > "CJ" wrote:
> > > 
> > > > I first messed with the Norton Firewall settings (which were really weird, 
> > > > because they had a "block windows file sharing" and an "allow windows file 
> > > > sharing" checkboxes and both were selected. :S) 
> > > > 
> > > > Then I tried to turn off password protection on the vista machine, but it 
> > > > kept on alerting me with "the parameter is incorrect." 
> > > > 
> > > > I ran the network setup wizard on one of the machines, but it didn't change 
> > > > anything. 
> > > > 
> > > > I tried plugging into the router because the vista laptop was connecting 
> > > > wirelessly and the XP desktops were wired. I ran the windows XP Network setup 
> > > > on the XP machines, but they still didn't detect the laptop even after I 
> > > > tried running the network setup disk on the laptop.
> > > > 
> > > > This is driving me nuts! I can't figure out what's wrong here.
> > > > 
> > > > "Mick Murphy" wrote:
> > > > 
> > > > > Have a read of info below, especially XP's file sharing Network wizard.
> > > > > 
> > > > > http://technet.microsoft.com/en-us/library/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 (or LAN allowed, depending on how their 
> > > > > Exceptions are worded in their Firewall)
> > > > > 
> > > > > 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 (passwords 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, run the XP’s Home or Small Office Network File and Printer Sharing 
> > > > > Wizard to include Vista in your “New” Network, even if you had an XP Network 
> > > > > set up prior to adding a Vista computer to it(redoing the Wizard seems to 
> > > > > work for XP machines!). 
> > > > > 
> > > > > In “My Network Places”: “Set up a Home or Small Office Network”
> > > > > OR under Accessories > Communications > Network Setup Wizard > Allow File 
> > > > > and Printer Sharing.
> > > > > 
> > > > > -- 
> > > > > Mick Murphy - Qld - Australia
> > > > > 
> > > > > 
> > > > > "CJ" wrote:
> > > > > 
> > > > > > I had no trouble connecting my laptop to my wireless router for internet 
> > > > > > access, but I cannot connect to my home network properly. I installed the 
> > > > > > LLTD Responder on the XP machines, and I can see them on the network map, but 
> > > > > > I cannot access their shared files, nor can I see them when I view the actual 
> > > > > > network. The Vista machines workgroup has the same name as the XP ones. BTW 
> > > > > > the XP machines can't seem to find the laptop either.

I hate to say this, but the network is no longer working. I can't understand 
what's going on! I can ping the IP and the computer names of the XP computers 
in the laptop's command prompt, but the XP computers can't ping the Vista 
laptop. This is the message I got when I tried (Comments and asterisks added):

Pinging ***.***.*.105 with 32 bytes of data:                          
//Asterisks added

Reply from ***.*.**.3: Destination net unreachable.               /*This is 
a different IP  that I can't figure out where it's from.*/
Request timed out.
Reply from ***.*.**.3: Destination net unreachable.
Reply from ***.*.**.3: Destination net unreachable.

Ping statistics for ***.***.*.105:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Is there a way in vista to connect to a computer by its IP? Oh, and another 
thing: the computers are showing in the network map as connected to "switch," 
which is connected to the router. The weird thing is, I can't click on them. 
Sorry to throw all this info at you at once; I admit I'm completely baffled 
by this.

On Tue, 19 Aug 2008 22:35:01 -0700, CJ 
wrote:

>I hate to say this, but the network is no longer working. I can't understand 
>what's going on! I can ping the IP and the computer names of the XP computers 
>in the laptop's command prompt, but the XP computers can't ping the Vista 
>laptop. This is the message I got when I tried (Comments and asterisks added):
>
>Pinging ***.***.*.105 with 32 bytes of data:                          
>//Asterisks added
>
>Reply from ***.*.**.3: Destination net unreachable.               /*This is 
>a different IP  that I can't figure out where it's from.*/
>Request timed out.
>Reply from ***.*.**.3: Destination net unreachable.
>Reply from ***.*.**.3: Destination net unreachable.
>
>Ping statistics for ***.***.*.105:
>    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
>Approximate round trip times in milli-seconds:
>    Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
>Is there a way in vista to connect to a computer by its IP? Oh, and another 
>thing: the computers are showing in the network map as connected to "switch," 
>which is connected to the router. The weird thing is, I can't click on them. 
>Sorry to throw all this info at you at once; I admit I'm completely baffled 
>by this.

Since you've concealed the actual IP addresses, it's hard for anyone
else to understand the problem.  I assume that your network uses
private IP addresses (10.x.x.x, 172.16.x.x, or 192.168.x.x).  In that
case, the addresses are local to your network and can't be accessed by
anyone from the Internet, so it's safe to show them.

I suggest that you post another message showing the full IP addresses,
and tell us which computer corresponds to which IP address and what
your router's LAN IP address is.  You can use the "-a" flag in the
"ping" command to identify the host name associated with an IP
address.  For example:

   ping -a 192.168.0.3
-- 
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see.  I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

OK, I just wasn't sure and had seen that done on other forums. Anyways, 
here's the message without asterisks:

Pinging 192.106.1.105 with 32 bytes of data:

Reply from 151.6.36.3: Destination net unreachable.
Request timed out.
Reply from 151.6.36.3: Destination net unreachable.
Reply from 151.6.36.3: Destination net unreachable.

Ping statistics for 192.106.1.105:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

"Steve Winograd" wrote:

> On Tue, 19 Aug 2008 22:35:01 -0700, CJ 
> wrote:
> 
> >I hate to say this, but the network is no longer working. I can't understand 
> >what's going on! I can ping the IP and the computer names of the XP computers 
> >in the laptop's command prompt, but the XP computers can't ping the Vista 
> >laptop. This is the message I got when I tried (Comments and asterisks added):
> >
> >Pinging ***.***.*.105 with 32 bytes of data:                          
> >//Asterisks added
> >
> >Reply from ***.*.**.3: Destination net unreachable.               /*This is 
> >a different IP  that I can't figure out where it's from.*/
> >Request timed out.
> >Reply from ***.*.**.3: Destination net unreachable.
> >Reply from ***.*.**.3: Destination net unreachable.
> >
> >Ping statistics for ***.***.*.105:
> >    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
> >Approximate round trip times in milli-seconds:
> >    Minimum = 0ms, Maximum = 0ms, Average = 0ms
> >
> >Is there a way in vista to connect to a computer by its IP? Oh, and another 
> >thing: the computers are showing in the network map as connected to "switch," 
> >which is connected to the router. The weird thing is, I can't click on them. 
> >Sorry to throw all this info at you at once; I admit I'm completely baffled 
> >by this.
> 
> Since you've concealed the actual IP addresses, it's hard for anyone
> else to understand the problem.  I assume that your network uses
> private IP addresses (10.x.x.x, 172.16.x.x, or 192.168.x.x).  In that
> case, the addresses are local to your network and can't be accessed by
> anyone from the Internet, so it's safe to show them.
> 
> I suggest that you post another message showing the full IP addresses,
> and tell us which computer corresponds to which IP address and what
> your router's LAN IP address is.  You can use the "-a" flag in the
> "ping" command to identify the host name associated with an IP
> address.  For example:
> 
>    ping -a 192.168.0.3
> -- 
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
> 
> Please post any reply as a follow-up message in the news group
> for everyone to see.  I'm sorry, but I don't answer questions
> addressed directly to me in E-mail or news groups.
> 
> Microsoft Most Valuable Professional Program
> http://mvp.support.microsoft.com
>

CJ wrote:

> OK, I just wasn't sure and had seen that done on other forums. Anyways,
> here's the message without asterisks:
> 
> Pinging 192.106.1.105 with 32 bytes of data:
> 
> Reply from 151.6.36.3: Destination net unreachable.
> Request timed out.
> Reply from 151.6.36.3: Destination net unreachable.
> Reply from 151.6.36.3: Destination net unreachable.
> 
> Ping statistics for 192.106.1.105:
>     Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
> Approximate round trip times in milli-seconds:
>     Minimum = 0ms, Maximum = 0ms, Average = 0ms

Well, there's your problem right there. The two computers are on completely
separate subnets. One is private (the 192 one) and one is public (or just
plain wrong, the 151 one). They will never speak to each other!

How is your network set up? Describe how you get to the Internet (method,
ISP) and exactly what equipment you have (make/model of items).

Malke
-- 
MS-MVP
Elephant Boy Computers - Don't Panic!
FAQ - http://www.elephantboycomputers.com/#FAQ

OK, I'm connecting to a linksys Wireless-G router wirelessly on the vista 
laptop and directly through the XP desktops. Here are all the text files 
Steve requested.

Vista Laptop:

ipconfig /all


Windows IP Configuration

   Host Name . . . . . . . . . . . . : Vista_Laptop
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : bc.hsia.telus.net

Ethernet adapter Bluetooth Network Connection 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Bluetooth Device (Personal Area 
Network) #2
   Physical Address. . . . . . . . . : 00-1F-E1-FE-72-D9
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . : bc.hsia.telus.net
   Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 4965AGN
   Physical Address. . . . . . . . . : 00-1F-3B-AA-F2-B7
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : 
fe80::49d1:7be0:ca8d:cd95%13(Preferred) 
   IPv4 Address. . . . . . . . . . . : 192.168.1.105(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : August-21-08 9:21:16 AM
   Lease Expires . . . . . . . . . . : August-22-08 9:21:16 AM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 75.154.133.68
                                       75.154.133.100
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : bc.hsia.telus.net
   Description . . . . . . . . . . . : Realtek RTL8101E Family PCI-E Fast 
Ethernet NIC (NDIS 6.0)
   Physical Address. . . . . . . . . : 00-21-CC-01-17-E1
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 
2001:0:4137:9e50:301b:2a5c:3027:f068(Preferred) 
   Link-local IPv6 Address . . . . . : 
fe80::301b:2a5c:3027:f068%16(Preferred) 
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 12:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : 
isatap.{6CD74E7F-D1DD-4DF8-97C1-B4D2BE2C96B6}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 14:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : bc.hsia.telus.net
   Description . . . . . . . . . . . : isatap.bc.hsia.telus.net
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
__________________________________________________________

route -4 print

===========================================================================
Interface List
 15 ...00 1f e1 fe 72 d9 ...... Bluetooth Device (Personal Area Network) #2
 13 ...00 1f 3b aa f2 b7 ...... Intel(R) Wireless WiFi Link 4965AGN
 10 ...00 21 cc 01 17 e1 ...... Realtek RTL8101E Family PCI-E Fast Ethernet 
NIC (NDIS 6.0)
  1 ........................... Software Loopback Interface 1
 16 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
 18 ...00 00 00 00 00 00 00 e0  isatap.{6CD74E7F-D1DD-4DF8-97C1-B4D2BE2C96B6}
 17 ...00 00 00 00 00 00 00 e0  isatap.bc.hsia.telus.net
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1    192.168.1.105     25
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      192.168.1.0    255.255.255.0         On-link     192.168.1.105    281
    192.168.1.105  255.255.255.255         On-link     192.168.1.105    281
    192.168.1.255  255.255.255.255         On-link     192.168.1.105    281
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link     192.168.1.105    281
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link     192.168.1.105    281
===========================================================================
Persistent Routes:
  None
__________________________________________________________

XP Desktop (I only did this on one of them; if you want me to do it on the 
other one I can)

ipconfig /all

Windows IP Configuration



        Host Name . . . . . . . . . . . . : PLAYROOM

        Primary Dns Suffix  . . . . . . . : 

        Node Type . . . . . . . . . . . . : Unknown

        IP Routing Enabled. . . . . . . . : No

        WINS Proxy Enabled. . . . . . . . : No

        DNS Suffix Search List. . . . . . : bc.hsia.telus.net



Ethernet adapter Local Area Connection:



        Connection-specific DNS Suffix  . : bc.hsia.telus.net

        Description . . . . . . . . . . . : Intel(R) PRO/100 VE Desktop 
Connection

        Physical Address. . . . . . . . . : 00-02-55-FF-0E-40

        Dhcp Enabled. . . . . . . . . . . : Yes

        Autoconfiguration Enabled . . . . : Yes

        IP Address. . . . . . . . . . . . : 192.168.1.106

        Subnet Mask . . . . . . . . . . . : 255.255.255.0

        Default Gateway . . . . . . . . . : 192.168.1.1

        DHCP Server . . . . . . . . . . . : 192.168.1.1

        DNS Servers . . . . . . . . . . . : 75.154.133.68

                                            75.154.133.100

        Lease Obtained. . . . . . . . . . : Thursday, August 21, 2008 
9:21:31 AM

        Lease Expires . . . . . . . . . . : Friday, August 22, 2008 9:21:31 AM
__________________________________________________________

route print

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 02 55 ff 0e 40 ...... Intel(R) PRO/100 VE Desktop Connection - 
Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1   192.168.1.106	  20
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1	  1
      192.168.1.0    255.255.255.0    192.168.1.106   192.168.1.106	  20
    192.168.1.106  255.255.255.255        127.0.0.1       127.0.0.1	  20
    192.168.1.255  255.255.255.255    192.168.1.106   192.168.1.106	  20
        224.0.0.0        240.0.0.0    192.168.1.106   192.168.1.106	  20
  255.255.255.255  255.255.255.255    192.168.1.106   192.168.1.106	  1
Default Gateway:       192.168.1.1
===========================================================================
Persistent Routes:
  None
__________________________________________________________

Hope that makes more sense to you than it does me!

The laptop pinged everything successfully, but the XP machine(playroom) 
couldn't ping the laptop either by name or IP. The requests would time out 
when I tried the IP, and it could not find the host name for the laptop. I 
was wondering why I didn't get the error message from the other IP (the 153 
one) like I did last time I pinged. 

"Steve Winograd" wrote:
 
> Thanks for posting the ipconfig and route information.  Everything
> looks normal on those two computers, which receive private IP
> addresses from your router.
> 
> The Vista laptop (Vista_Laptop) is 192.168.1.105, the XP desktop
> (PLAYROOM) is 192.168.1.106, and the router is 192.168.1.1.
> 
> Unfortunately, this gives no clue to the problem.  Based on what
> appears here, the computers should be able to ping each other
> successfully.  What are the results of running each of these commands
> on each computer?
> 
>    ping 192.168.1.105
>    ping 192.168.1.106
>    ping vista_laptop
>    ping playroom
> -- 
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
> 
> Please post any reply as a follow-up message in the news group
> for everyone to see.  I'm sorry, but I don't answer questions
> addressed directly to me in E-mail or news groups.
> 
> Microsoft Most Valuable Professional Program
> http://mvp.support.microsoft.com
>

Thanks, Steve! Norton was the problem (what a surprise). I disabled Norton's 
Firewall entirely since I have Vista's on anyway, and now the network works 
perfectly! Thanks so much for your help.

"Steve Winograd" wrote:
> 
> I can't explain why the 153 address showed up in your earlier ping
> result.  Given the ipconfig and route information you posted, that
> address makes no sense.
> 
> It's possible that the laptop has a firewall program (Norton, McAfee,
> ZoneAlarm, PC-cillin, etc) or Vista's built-in Windows Firewall that's
> blocking access.  Make sure that any firewall is configured to allow
> access by other computers on the LAN.  Note that some antivirus
> programs have firewall components that have to be configured.  An
> example is Norton Antivirus' "Internet Worm Protection".
> 
> Start both computers in "Safe mode with networking" and try the pings.
> If they work in that mode, a firewall is almost certainly causing the
> problem in normal mode.
> -- 
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
> 
> Please post any reply as a follow-up message in the news group
> for everyone to see.  I'm sorry, but I don't answer questions
> addressed directly to me in E-mail or news groups.
> 
> Microsoft Most Valuable Professional Program
> http://mvp.support.microsoft.com
>