Networking XP computers w Vista Computers

I have just switched to a brand new Vista computer as the primary computer on
my network. I even got Ultimate to have the best. Now I can't see the other
computer on the network because it has been determined to be a "has been",
what with only having XP on it.

I have searched high and low, talked to people who [should] know, and have
yet to hear someone explain how it is that MicroSoft, in all of its glory,
could launch such a major marketing campaign to get us to all sign on to the
new OS ... they never thought to think that maybe, just maybe ... someone
somewhere just might want to have an XP computer exist in peace and harmony
with a Vista computer?????

Now you're saying that I should call tech support ... fabulous idea, in fact
I did that very thing ... started with HP cuz it's their computer but "That's
a Microsoft problem, you gotta call them" ... okie dokie, call Microsoft but
damned if "HP is supposed to troubleshoot it cuz it came on their computer"
.... what fun, so call back HP, get a bit ****y, he tries to help, tells me to
d/l a patch from Microsoft.com, which I do ... the excitement is building,
we're gonna resolve the problem with a patch, yeah!!! ... re-boot everything
and .... and ... nothing, nada, nyet. Then he tells me I can pay $69.99 to
talk to their networking dudes who may or may not be able to help me. So,
here we are now ........

I mean, come on now ... let's THINK PEOPLE!!!!!! There needs to be a fix to
this NOW to let these computers do what they are supposed to do!!! This is a
step backwards!! This should have been anticipated and worked out PRIOR to
letting the world buy it and screw up their small network connectivity. I
doubt if I am the only one that doesn't have the cash to just run out and
update all my computers and/or operating systems every time MicroSoft decided
to lauch a new version of Windows!

Undoubtedly, someone will offer apologies, and ineffectual explanations ...
bottom line is that this isn't an uncommon thing and I can't think of any
[rational] argument to convince me that it should not have been taken care of
before the launch. It doesn't matter if it's a cable problem, OS problem,
security problem, whatever ... We don't care why it isn't working, just get
it fixed so it does work!!!!!! You had time to spend moving all the buttons
around so we get to play hide and seek finding them, the least you could do
is retain the previous networking functionality!!

Anyone out there that can shed some light on this ... and more importantly,
how to overcome this problem ... all in language that us
non-brilliant-tecchies can understand?????

"Dave B" <Dave > wrote in message
news:351A100D-9C42-4AA8-85A5-...

> I have searched high and low, talked to people who [should] know, and have
> yet to hear someone explain how it is that MicroSoft, in all of its glory,
> could launch such a major marketing campaign to get us to all sign on to
> the
> new OS ... they never thought to think that maybe, just maybe ... someone
> somewhere just might want to have an XP computer exist in peace and
> harmony
> with a Vista computer?????


I'm guessing -- purely a guess -- that this is not a Vista problem. My Vista
computer connects to a network that has an XP computer on it.
You're right to be ****ed that it doesn't work. So far all your venom is
aimed at MS. But what if the problem lies elsewhere?

where else exactly could the problem lie?? All you have to do is read the
posts to conclude the obvious, it's not just me or anyone else ... whether
the problem lies in XP or Vista or both, Microsoft should have realized the
problem and solved it before release, it's a simple thing really!!! They can
fix both programs with their incessant updates whenever they want, they could
have solved it without all this hullaballoo!!

Let's be logical ... I could plug in a new XP computer to another and
voila!, there it is, we're set to go ... now I do that and I can't even get
it to work after hours of frustration, endless online chats and rooms, phone
support from MS and HP, both of whom acknowledge that "there is a known issue
...." ... DUH!! FIX IT!!!

"DP" wrote:

>
> "Dave B" <Dave > wrote in message
> news:351A100D-9C42-4AA8-85A5-...
>
> > I have searched high and low, talked to people who [should] know, and have
> > yet to hear someone explain how it is that MicroSoft, in all of its glory,
> > could launch such a major marketing campaign to get us to all sign on to
> > the
> > new OS ... they never thought to think that maybe, just maybe ... someone
> > somewhere just might want to have an XP computer exist in peace and
> > harmony
> > with a Vista computer?????
>
>
> I'm guessing -- purely a guess -- that this is not a Vista problem. My Vista
> computer connects to a network that has an XP computer on it.
> You're right to be ****ed that it doesn't work. So far all your venom is
> aimed at MS. But what if the problem lies elsewhere?
>
>

On Sat, 21 Jul 2007 11:20:01 -0700, Dave B <Dave
> wrote:

>I have just switched to a brand new Vista computer as the primary computer on
>my network. I even got Ultimate to have the best. Now I can't see the other
>computer on the network because it has been determined to be a "has been",
>what with only having XP on it.
>
>I have searched high and low, talked to people who [should] know, and have
>yet to hear someone explain how it is that MicroSoft, in all of its glory,
>could launch such a major marketing campaign to get us to all sign on to the
>new OS ... they never thought to think that maybe, just maybe ... someone
>somewhere just might want to have an XP computer exist in peace and harmony
>with a Vista computer?????
>
>Now you're saying that I should call tech support ... fabulous idea, in fact
>I did that very thing ... started with HP cuz it's their computer but "That's
>a Microsoft problem, you gotta call them" ... okie dokie, call Microsoft but
>damned if "HP is supposed to troubleshoot it cuz it came on their computer"
>... what fun, so call back HP, get a bit ****y, he tries to help, tells me to
>d/l a patch from Microsoft.com, which I do ... the excitement is building,
>we're gonna resolve the problem with a patch, yeah!!! ... re-boot everything
>and .... and ... nothing, nada, nyet. Then he tells me I can pay $69.99 to
>talk to their networking dudes who may or may not be able to help me. So,
>here we are now ........
>
>I mean, come on now ... let's THINK PEOPLE!!!!!! There needs to be a fix to
>this NOW to let these computers do what they are supposed to do!!! This is a
>step backwards!! This should have been anticipated and worked out PRIOR to
>letting the world buy it and screw up their small network connectivity. I
>doubt if I am the only one that doesn't have the cash to just run out and
>update all my computers and/or operating systems every time MicroSoft decided
>to lauch a new version of Windows!
>
>Undoubtedly, someone will offer apologies, and ineffectual explanations ...
>bottom line is that this isn't an uncommon thing and I can't think of any
>[rational] argument to convince me that it should not have been taken care of
>before the launch. It doesn't matter if it's a cable problem, OS problem,
>security problem, whatever ... We don't care why it isn't working, just get
>it fixed so it does work!!!!!! You had time to spend moving all the buttons
>around so we get to play hide and seek finding them, the least you could do
>is retain the previous networking functionality!!
>
>Anyone out there that can shed some light on this ... and more importantly,
>how to overcome this problem ... all in language that us
>non-brilliant-tecchies can understand?????
I use network magic to network xp and vista.. no problems.. during
install, it takes a couple of reboots that setup forgets to tell you
about.. works great though..
Chuck (in SC)

"Dave B" <Dave > wrote in message
news:351A100D-9C42-4AA8-85A5-...
>I have just switched to a brand new Vista computer as the primary computer
>on
> my network. I even got Ultimate to have the best. Now I can't see the
> other
> computer on the network because it has been determined to be a "has been",
> what with only having XP on it.
>
> I have searched high and low, talked to people who [should] know, and have
> yet to hear someone explain how it is that MicroSoft, in all of its glory,
> could launch such a major marketing campaign to get us to all sign on to
> the
> new OS ... they never thought to think that maybe, just maybe ... someone
> somewhere just might want to have an XP computer exist in peace and
> harmony
> with a Vista computer?????
>
> Now you're saying that I should call tech support ... fabulous idea, in
> fact
> I did that very thing ... started with HP cuz it's their computer but
> "That's
> a Microsoft problem, you gotta call them" ... okie dokie, call Microsoft
> but
> damned if "HP is supposed to troubleshoot it cuz it came on their
> computer"
> ... what fun, so call back HP, get a bit ****y, he tries to help, tells me
> to
> d/l a patch from Microsoft.com, which I do ... the excitement is building,
> we're gonna resolve the problem with a patch, yeah!!! ... re-boot
> everything
> and .... and ... nothing, nada, nyet. Then he tells me I can pay $69.99
> to
> talk to their networking dudes who may or may not be able to help me. So,
> here we are now ........
>
> I mean, come on now ... let's THINK PEOPLE!!!!!! There needs to be a fix
> to
> this NOW to let these computers do what they are supposed to do!!! This
> is a
> step backwards!! This should have been anticipated and worked out PRIOR
> to
> letting the world buy it and screw up their small network connectivity. I
> doubt if I am the only one that doesn't have the cash to just run out and
> update all my computers and/or operating systems every time MicroSoft
> decided
> to lauch a new version of Windows!
>
> Undoubtedly, someone will offer apologies, and ineffectual explanations
> ...
> bottom line is that this isn't an uncommon thing and I can't think of any
> [rational] argument to convince me that it should not have been taken care
> of
> before the launch. It doesn't matter if it's a cable problem, OS problem,
> security problem, whatever ... We don't care why it isn't working, just
> get
> it fixed so it does work!!!!!! You had time to spend moving all the
> buttons
> around so we get to play hide and seek finding them, the least you could
> do
> is retain the previous networking functionality!!
>
> Anyone out there that can shed some light on this ... and more
> importantly,
> how to overcome this problem ... all in language that us
> non-brilliant-tecchies can understand?????

Seem my post a few posts earlier "Vista & XP Network woes"

In article <351A100D-9C42-4AA8-85A5->,
Dave B <Dave > wrote:


> I have searched high and low, talked to people who [should] know, and have
> yet to hear someone explain how it is that MicroSoft, in all of its glory,
> could launch such a major marketing campaign to get us to all sign on to the
> new OS ... they never thought to think that maybe, just maybe ... someone
> somewhere just might want to have an XP computer exist in peace and harmony
> with a Vista computer?????

Um, they did. It works. Well, it works here. I see Vista machines,
XP machines and OS X machines from any machine on my network. Wired,
wireless, makes no difference. They all play together.

But this is the 2nd post today of someone having problems connecting a
Vista machine to an XP machine.

Weird.

Mike

Dave B wrote:

> I have just switched to a brand new Vista computer as the primary
> computer on my network. I even got Ultimate to have the best. Now I
> can't see the other computer on the network because it has been
> determined to be a "has been", what with only having XP on it.
>
> I have searched high and low, talked to people who [should] know, and
> have yet to hear someone explain how it is that MicroSoft, in all of
> its glory, could launch such a major marketing campaign to get us to
> all sign on to the new OS ... they never thought to think that maybe,
> just maybe ... someone somewhere just might want to have an XP
> computer exist in peace and harmony with a Vista computer?????
>
> Now you're saying that I should call tech support ... fabulous idea,
> in fact I did that very thing ... started with HP cuz it's their
> computer but "That's a Microsoft problem, you gotta call them" ...
> okie dokie, call Microsoft but damned if "HP is supposed to
> troubleshoot it cuz it came on their computer" ... what fun, so call
> back HP, get a bit ****y, he tries to help, tells me to d/l a patch
> from Microsoft.com, which I do ... the excitement is building, we're
> gonna resolve the problem with a patch, yeah!!! ... re-boot
> everything and .... and ... nothing, nada, nyet. Then he tells me I
> can pay $69.99 to talk to their networking dudes who may or may not
> be able to help me. So, here we are now ........
>
> I mean, come on now ... let's THINK PEOPLE!!!!!! There needs to be a
> fix to this NOW to let these computers do what they are supposed to
> do!!! This is a step backwards!! This should have been anticipated
> and worked out PRIOR to letting the world buy it and screw up their
> small network connectivity. I doubt if I am the only one that
> doesn't have the cash to just run out and update all my computers
> and/or operating systems every time MicroSoft decided to lauch a new
> version of Windows!
>
> Undoubtedly, someone will offer apologies, and ineffectual
> explanations ... bottom line is that this isn't an uncommon thing
> and I can't think of any [rational] argument to convince me that it
> should not have been taken care of before the launch. It doesn't
> matter if it's a cable problem, OS problem, security problem,
> whatever ... We don't care why it isn't working, just get it fixed so
> it does work!!!!!! You had time to spend moving all the buttons
> around so we get to play hide and seek finding them, the least you
> could do is retain the previous networking functionality!!
>
> Anyone out there that can shed some light on this ... and more
> importantly, how to overcome this problem ... all in language that us
> non-brilliant-tecchies can understand?????

I had this issue - problem solved by MS in article KB922120 which is
a down-load to place on each XP machine - makes them visible to Vista
machines allowing a full newtwrok map to be produced.

Mick

--

Their website description looks promising ... thanks!! Is there anyone else
with experience, good or bad, with the network magic software (or a
comparable third party software)??

I find it absolutely amazing that someone else could come up with a way to
connect XP to Vista before Microsoft could do it??? Heya Bill ... R&D means
Research and Development, the implication being that you use that time and
all the geniuses around the table to actually research the obvious, staring
you in the your face problems!!

Then again, this could just be a way to get us to all run out and buy Vista,
what with all of Microsoft's financial woes of late ... can't you just
imagine them sitting around the table talking about it and some marketing
genius says "well, ah, Boss ... if don't let them talk to each other, then
everyone will just have to go out and buy more Vista ... we'll tell them
we're improving their experience and making them more secure and they'll just
do it out of frustration in trying to get us to stop the doublespeak and fix
it like we shouldda before we released it. I mean, c'mon boss, it's not our
fault if they can't get the right software on all their computers, eh??

"Chuck (in SC)" wrote:

> On Sat, 21 Jul 2007 11:20:01 -0700, Dave B <Dave
> > wrote:
>
> >I have just switched to a brand new Vista computer as the primary computer on
> >my network. I even got Ultimate to have the best. Now I can't see the other
> >computer on the network because it has been determined to be a "has been",
> >what with only having XP on it.
> >
> >I have searched high and low, talked to people who [should] know, and have
> >yet to hear someone explain how it is that MicroSoft, in all of its glory,
> >could launch such a major marketing campaign to get us to all sign on to the
> >new OS ... they never thought to think that maybe, just maybe ... someone
> >somewhere just might want to have an XP computer exist in peace and harmony
> >with a Vista computer?????
> >
> >Now you're saying that I should call tech support ... fabulous idea, in fact
> >I did that very thing ... started with HP cuz it's their computer but "That's
> >a Microsoft problem, you gotta call them" ... okie dokie, call Microsoft but
> >damned if "HP is supposed to troubleshoot it cuz it came on their computer"
> >... what fun, so call back HP, get a bit ****y, he tries to help, tells me to
> >d/l a patch from Microsoft.com, which I do ... the excitement is building,
> >we're gonna resolve the problem with a patch, yeah!!! ... re-boot everything
> >and .... and ... nothing, nada, nyet. Then he tells me I can pay $69.99 to
> >talk to their networking dudes who may or may not be able to help me. So,
> >here we are now ........
> >
> >I mean, come on now ... let's THINK PEOPLE!!!!!! There needs to be a fix to
> >this NOW to let these computers do what they are supposed to do!!! This is a
> >step backwards!! This should have been anticipated and worked out PRIOR to
> >letting the world buy it and screw up their small network connectivity. I
> >doubt if I am the only one that doesn't have the cash to just run out and
> >update all my computers and/or operating systems every time MicroSoft decided
> >to lauch a new version of Windows!
> >
> >Undoubtedly, someone will offer apologies, and ineffectual explanations ...
> >bottom line is that this isn't an uncommon thing and I can't think of any
> >[rational] argument to convince me that it should not have been taken care of
> >before the launch. It doesn't matter if it's a cable problem, OS problem,
> >security problem, whatever ... We don't care why it isn't working, just get
> >it fixed so it does work!!!!!! You had time to spend moving all the buttons
> >around so we get to play hide and seek finding them, the least you could do
> >is retain the previous networking functionality!!
> >
> >Anyone out there that can shed some light on this ... and more importantly,
> >how to overcome this problem ... all in language that us
> >non-brilliant-tecchies can understand?????
> I use network magic to network xp and vista.. no problems.. during
> install, it takes a couple of reboots that setup forgets to tell you
> about.. works great though..
> Chuck (in SC)
>

<Chuck (in SC)> wrote in message
news:...
> On Sat, 21 Jul 2007 11:20:01 -0700, Dave B <Dave
> > wrote:
>
>>I have just switched to a brand new Vista computer as the primary computer
>>on
>>my network. I even got Ultimate to have the best. Now I can't see the
>>other
>>computer on the network because it has been determined to be a "has been",
>>what with only having XP on it.
>>
>>I have searched high and low, talked to people who [should] know, and have
>>yet to hear someone explain how it is that MicroSoft, in all of its glory,
>>could launch such a major marketing campaign to get us to all sign on to
>>the
>>new OS ... they never thought to think that maybe, just maybe ... someone
>>somewhere just might want to have an XP computer exist in peace and
>>harmony
>>with a Vista computer?????
>>
>>Now you're saying that I should call tech support ... fabulous idea, in
>>fact
>>I did that very thing ... started with HP cuz it's their computer but
>>"That's
>>a Microsoft problem, you gotta call them" ... okie dokie, call Microsoft
>>but
>>damned if "HP is supposed to troubleshoot it cuz it came on their
>>computer"
>>... what fun, so call back HP, get a bit ****y, he tries to help, tells me
>>to
>>d/l a patch from Microsoft.com, which I do ... the excitement is building,
>>we're gonna resolve the problem with a patch, yeah!!! ... re-boot
>>everything
>>and .... and ... nothing, nada, nyet. Then he tells me I can pay $69.99
>>to
>>talk to their networking dudes who may or may not be able to help me. So,
>>here we are now ........
>>
>>I mean, come on now ... let's THINK PEOPLE!!!!!! There needs to be a fix
>>to
>>this NOW to let these computers do what they are supposed to do!!! This
>>is a
>>step backwards!! This should have been anticipated and worked out PRIOR
>>to
>>letting the world buy it and screw up their small network connectivity. I
>>doubt if I am the only one that doesn't have the cash to just run out and
>>update all my computers and/or operating systems every time MicroSoft
>>decided
>>to lauch a new version of Windows!
>>
>>Undoubtedly, someone will offer apologies, and ineffectual explanations
>>...
>>bottom line is that this isn't an uncommon thing and I can't think of any
>>[rational] argument to convince me that it should not have been taken care
>>of
>>before the launch. It doesn't matter if it's a cable problem, OS problem,
>>security problem, whatever ... We don't care why it isn't working, just
>>get
>>it fixed so it does work!!!!!! You had time to spend moving all the
>>buttons
>>around so we get to play hide and seek finding them, the least you could
>>do
>>is retain the previous networking functionality!!
>>
>>Anyone out there that can shed some light on this ... and more
>>importantly,
>>how to overcome this problem ... all in language that us
>>non-brilliant-tecchies can understand?????
> I use network magic to network xp and vista.. no problems.. during
> install, it takes a couple of reboots that setup forgets to tell you
> about.. works great though..
> Chuck (in SC)

See my earlier post, i tried network magic, only problem is it only works on
routet networks, i'm using a crossover cable D'oh

"Mick" <> wrote in message
news:...
> Dave B wrote:
>
>> I have just switched to a brand new Vista computer as the primary
>> computer on my network. I even got Ultimate to have the best. Now I
>> can't see the other computer on the network because it has been
>> determined to be a "has been", what with only having XP on it.
>>
>> I have searched high and low, talked to people who [should] know, and
>> have yet to hear someone explain how it is that MicroSoft, in all of
>> its glory, could launch such a major marketing campaign to get us to
>> all sign on to the new OS ... they never thought to think that maybe,
>> just maybe ... someone somewhere just might want to have an XP
>> computer exist in peace and harmony with a Vista computer?????
>>
>> Now you're saying that I should call tech support ... fabulous idea,
>> in fact I did that very thing ... started with HP cuz it's their
>> computer but "That's a Microsoft problem, you gotta call them" ...
>> okie dokie, call Microsoft but damned if "HP is supposed to
>> troubleshoot it cuz it came on their computer" ... what fun, so call
>> back HP, get a bit ****y, he tries to help, tells me to d/l a patch
>> from Microsoft.com, which I do ... the excitement is building, we're
>> gonna resolve the problem with a patch, yeah!!! ... re-boot
>> everything and .... and ... nothing, nada, nyet. Then he tells me I
>> can pay $69.99 to talk to their networking dudes who may or may not
>> be able to help me. So, here we are now ........
>>
>> I mean, come on now ... let's THINK PEOPLE!!!!!! There needs to be a
>> fix to this NOW to let these computers do what they are supposed to
>> do!!! This is a step backwards!! This should have been anticipated
>> and worked out PRIOR to letting the world buy it and screw up their
>> small network connectivity. I doubt if I am the only one that
>> doesn't have the cash to just run out and update all my computers
>> and/or operating systems every time MicroSoft decided to lauch a new
>> version of Windows!
>>
>> Undoubtedly, someone will offer apologies, and ineffectual
>> explanations ... bottom line is that this isn't an uncommon thing
>> and I can't think of any [rational] argument to convince me that it
>> should not have been taken care of before the launch. It doesn't
>> matter if it's a cable problem, OS problem, security problem,
>> whatever ... We don't care why it isn't working, just get it fixed so
>> it does work!!!!!! You had time to spend moving all the buttons
>> around so we get to play hide and seek finding them, the least you
>> could do is retain the previous networking functionality!!
>>
>> Anyone out there that can shed some light on this ... and more
>> importantly, how to overcome this problem ... all in language that us
>> non-brilliant-tecchies can understand?????
>
> I had this issue - problem solved by MS in article KB922120 which is
> a down-load to place on each XP machine - makes them visible to Vista
> machines allowing a full newtwrok map to be produced.
>
> Mick
>
> --
I d/loaded this patch and put it on my XP machine but the vista machine
still wont let me access the XP machine