Vista doesn't really show the other PCs on the network.

[Guest]

Hi,
I don't know if i'm posting it to the right place but dame i couldn't find
any where else to post. I have installed windows vista and i was happy lad at
first sight but afterwards well..........
I have a wireless router and some other PCs with XP professional are
connected to it but i can't just see them in networking. I'm connect with the
router fine and there aren't any problems accessing internet. I have tried to
take off firewall no luck don't have any other program that could affect it.
I tried to check for the workgroup and modify the workgroup and still no
luck. All the settings are correct and when i diagnose it doesn't show any
problem but no PCs. Ironically both of the others can see each other except
my vista laptop. I thought Ms suppose to make it easy but its even difficult
to do anything with the network here........ I'm just struggling.
Any ideas?

Thanks

 

[Bill Sanderson MVP]

Do you have the same workgroup name set on the Vista machine as on the XP
machines?

For sophisticated network mapping, there is an update which you should apply
to the XP machines:

http://www.microsoft.com/downloads/...1d-ee46-481e-ba11-37f485fa34ea&displaylang=en

If the machines are in a domain, you will need to tweak a group policy
setting on each machine to enable the protocol to be used.

 

[Guest]

Hi Bill,

Thank you for your reply. All the system are on a workgroup and apart from
my vista they are all okay meaning they can view each other. It is just my
vista machine. I'll take a look at the link which you gave me and then report
it further afterwards but i'm greatly disappointed as the three keywords
relating to vista doesn't make any sense over here to me. The vista notebook
should be able to view the other PCs without installing an LLTD responder. So
i'm correct in guessing that i can't use vista with my existing network or
any other network of our suppliers as I have to install this LLTD on each
machine running windows XP professional and windows server 2003.
No disrespect to you but this just planily sucks, I'm sorry to say and it
hurts (as i'm an open supporter of MS) but I don't know how we ever gonna
compete with Mac Leopard this way.



---------------------------------
Supes | Trying to find my place

Do you have the same workgroup name set on the Vista machine as on the XP
machines?

For sophisticated network mapping, there is an update which you should apply
to the XP machines:

http://www.microsoft.com/downloads/...1d-ee46-481e-ba11-37f485fa34ea&displaylang=en

If the machines are in a domain, you will need to tweak a group policy
setting on each machine to enable the protocol to be used.

--

 

[Bill Sanderson MVP]

I probably shouldn't have posted that bit about the LLTD responder--'cause
it was clearly misleading. It is an aid for home networks--it can make some
things really easy, and it can also do some useful technical magic to do
with assuring that some traffic has priority over other traffic, and helping
home networkers provide better performance--for example when Voice over IP
and gaming both compete for bandwidth.

But--it isn't necessary for the same kind of connectivity that was available
with Windows for Workgroups and newer versions of Windows.

What is necessary are the same basics that always were: The same workgroup
name, unique machine names, and a common protocol--preferably TCP/IP.

If you've checked and the workgroup name is the same (is that "workgroup"?)
that's one hurdle cleared. The name doesn't matter, but it must be the same
for all of the machines for easy browsing.

Have you tried connecting by IP address?

You can find the IP address of each machine by going to a command prompt and
typing "ipconfig" and hitting enter. In Vista, there's enough additional
information that you may want to do "ipconfig |more" so that you can spot
the IPv4 address which comes early.

If all the IP addresses are on the same subnet (post them, and we can tell
you, if you don't know what that means)--then the machines should be able to
communicate.

Even if browsing isn't working, you should be able to do start, run,
\\192.168.1.22 <enter> (where 192.168.1.22 is the IP address of one of the
XP machines, for example.

Rather than try to go into full detail here (and probably not very
systematically--I haven't done this kind of support for a while)--I'd
recommend the two links under "home networking" at this URL:

http://www.microsoft.com/technet/windowsvista/network/default.mspx

They should help. I'm not sure whether your issue is firewall-related, or
whether there's an addressing or naming issue of some sort--so check those
articles, and let me know whether they help--or where you get stuck?

--

Hi Bill,

Thank you for your reply. All the system are on a workgroup and apart from
my vista they are all okay meaning they can view each other. It is just my
vista machine. I'll take a look at the link which you gave me and then
report
it further afterwards but i'm greatly disappointed as the three keywords
relating to vista doesn't make any sense over here to me. The vista
notebook
should be able to view the other PCs without installing an LLTD responder.
So
i'm correct in guessing that i can't use vista with my existing network or
any other network of our suppliers as I have to install this LLTD on each
machine running windows XP professional and windows server 2003.
No disrespect to you but this just planily sucks, I'm sorry to say and it
hurts (as i'm an open supporter of MS) but I don't know how we ever gonna
compete with Mac Leopard this way.

 

[Guest]

I have a Vista box at home and just added another XP box to my network. I
could do a remote login fine using the IP address on my network but was not
getting the Vista box to see the XP in the Network view. I did add LLTD to
the XP and Vista now reports the XP box. Just another user's experience.

 

[Bill Sanderson MVP]

XP and Vista use different default settings for "workgroup."

So--unless you chose a particular value for that they are likely different.
Try making them the same and see if that makes a difference.



--