What happend, thought things were to get better?

[Steve]

I thought with each successive update things would get better on Vista. Not
the case with the last update, it indicates it was security updates.

All was working fine with my network between the XP and Vista computers.

Since the last update I am suffering the same problem as a lot of people
here. My network disconnects at the XP home computer. I can boot the Vista
computer all I want but will not bring back the shares, the best I can do is
see the XP computer. A cold boot of the XP computer is the only thing that
will bring back the shares. Particularly frustrating since the printer is on
the XP computer. At times it will magically disappear for no reason, a
spontaneous disconnection of shares.

What is going on here, is there to be a fix soon?

Steve

 

[Rod Davies]

Ah yeah, I had the security update install fine on my Vista PC today and now
you mention it, that was when all of a sudden I no longer see the XP machine
on my workgroup...

....mmm...

Rgds

 

[Guest]

Steve I know your feeling. Same thing with me and my Printer...No-one so far
can give you a clear cut advice on how to reslove this.

I dont think it can be resloved....Had Geek Squad out to reslove my
issue....and that right after 2hr's they couldn't figure it out.

 

[Guest]

I thought with each successive update things would get better on Vista. Not
the case with the last update, it indicates it was security updates.

All was working fine with my network between the XP and Vista computers.

Since the last update I am suffering the same problem as a lot of people
here. My network disconnects at the XP home computer. I can boot the Vista
computer all I want but will not bring back the shares, the best I can do is
see the XP computer. A cold boot of the XP computer is the only thing that
will bring back the shares. Particularly frustrating since the printer is on
the XP computer. At times it will magically disappear for no reason, a
spontaneous disconnection of shares.

What is going on here, is there to be a fix soon?

Steve

 

[Steve]

It is very annoying, more then annoying, anger inducing, that Microsoft
would release Vista with such a huge problem. How could this have been
missed. It goes beyond an oversight and borders on arrogance, arrogance
thinking why bother with backward compatibility everyone will just switch at
any cost to our latest product.

Hopefully they have dedicated large resources for a real quick fix.

I am fed up with having to reboot the XP computer every time I need to
access files or the printer, sometimes I need to reboot more then once, even
then it is only available for a short period of time before I get kicked off
the network. I have experimented and the two XP computers remain contacted,
the Vista computer is the one getting kicked out. It would be interesting to
have another Vista computer to see what happens.

I know this is of no help, but just need to vent. maybe my displeasure will
get passed to Microsoft.

Steve

 

[cquirke (MVP Windows shell/user)]

On Sun, 8 Apr 2007 07:58:20 -0400, "Steve" <[email protected]>

Just for the fun of it, I'm going to start parsing complaints about
"buggy Vista" as if they were code...

It is very annoying, more then annoying, anger inducing, that Microsoft
would release Vista with such a huge problem.

Error: Unresolved forward link
Detail: Top-post without explicit context reference

How could this have been missed.

Error: Bad pointer 'this'

It goes beyond an oversight and borders on arrogance, arrogance
thinking why bother with backward compatibility everyone will just
switch at any cost to our latest product.

Error: Bad pointer 'it'

Hopefully they have dedicated large resources for a real quick fix.

Fix of what?

I am fed up with having to reboot the XP computer every time I need to
access files or the printer, sometimes I need to reboot more then once, even
then it is only available for a short period of time before I get kicked off
the network. I have experimented and the two XP computers remain contacted,
the Vista computer is the one getting kicked out. It would be interesting to
have another Vista computer to see what happens.

Ah, so it's resources on the Vista PC that you cannot consistently
access from the XP systems.

How many PCs on the LAN?
How are they cabled or WiFi'd?
How are IP addresses assigned?
Are they in the same workgroup?
Are there any servers involved?
Are you using LM hashes to authenticate?
Are you using the same user accounts?

I know this is of no help, but just need to vent. maybe my displeasure will
get passed to Microsoft.

Displeasure is cheap (there's always some out there, somewhere) and
usually discounted. What is more useful (but harder to provide) is
tech details that make it possible pin down bugs and fix them.

Still looking for pindown on "this" (yep, I'm late-to-thread)

As you can still "see" the other way round, it looks like cabling and
TCP/IP are OK. So why would shares "disappear"?

Reasons that suggest themselves are some sort of authentrication
hassle, or "too many" systems trying to enter the same system. MS
imposes arbitrary limits for licensing reasons; Win95/98 and the "pro"
versions of NT/2000/XP can accept 10 incoming connects, whereas WinME
and XP Home accept only 5. Dunno about Vista.

Are these PCs suspending at any time while this is going on, or
logging out when the screensaver comes on?

Is the printer suspending itself at some point?

Does Ping work, to confirm PCs are still visible at the raw TCP/IP
level in both directions?

Any add-on firewall software involved?

Does it help to use static IP addresses?

Sounds pretty awful. Can you pin this down to a particular update, or
at least, and update "day"?

---------- ----- ---- --- -- - - - -

On the 'net, *everyone* can hear you scream

 

[Steve]

How many PCs on the LAN?

For me it is three, 1 desktop, with XP home, one Laptop with Vista home
premium, the third is off most times, it is a XP home lapto[

How are they cabled or WiFi'd?

They are cabked and WiFid

How are IP addresses assigned?

Not static, my provider does not support that

Are they in the same workgroup?
yep

Are there any servers involved?
nope

Are you using LM hashes to authenticate?

what that?

Are you using the same user accounts?

each couputer has the same accounts, and passwords

As you can still "see" the other way round, it looks like cabling and
TCP/IP are OK. So why would shares "disappear"?

Reasons that suggest themselves are some sort of authentrication
hassle, or "too many" systems trying to enter the same system. MS
imposes arbitrary limits for licensing reasons; Win95/98 and the "pro"
versions of NT/2000/XP can accept 10 incoming connects, whereas WinME
and XP Home accept only 5. Dunno about Vista.

Are these PCs suspending at any time while this is going on, or
logging out when the screensaver comes on?

the network comes up only when the XP machine is booted after the Vista
computer, the shares eventually just drop, nothing happens prior to it
happening

Any add-on firewall software involved?

Firewalls are turned off and it still happens

Does it help to use static IP addresses?

Haven't tried that yet will give it a go.

Sounds pretty awful. Can you pin this down to a particular update, or
at least, and update "day"?

KB925002 4/42007

 

[Guest]

A software salesman told me last week that MS has recalled all XP and
deliberately made Vista difficult or impossible to cooperate with XP. He
seems to have hit the nail on the head. I'm about ready to smash this
machine, when in fact it's MS's fault - or should I say PLAN to control the
entire market, again. It is very frustrating. Their own support staff
really don't know what to do so they shuffle us sideways hoping for someone
to find real answers.

In the meantime... I'm still trying to get my Vista and XP to see one
another and share. I figure I will have to use a thumb drive and manually
slide things across.

 

[cquirke (MVP Windows shell/user)]

cquirke said

For me it is three, 1 desktop, with XP home, one Laptop with Vista home
premium, the third is off most times, it is a XP home lapto[

OK; even the most miserly OS limit should manage that, even with bugs
that see the PC itself as an "incoming connection".

They are cabked and WiFid

OK... which is WiFi'd, and how?

If your WiFi's gaping so that the whole neighborhood is part of your
LAN, then you may have "too many" incoming connects for the OS limit,
and that could blow you off.

Suspect this if "open", WEP, or WPA with < 8 character key.

Not static, my provider does not support that

Not the global IP assigned by the ISP on the WAN side; thinking more
of the internal IP addresses on the LAN side.

yep

Guuud... apparenly this now matters, in Vista.

nope

That makes it easier for me ;-)

what that?

LM hashes are detail within the way that users authenticate when
logging in to a network. It's an old way of holding the password that
has been crackable for a while now, and Vista finally chucks it out.

each couputer has the same accounts, and passwords
OK.


the network comes up only when the XP machine is booted after the Vista
computer, the shares eventually just drop, nothing happens prior to it
happening

Specifically, none of the machines go screen saver and "welcome"
screen, or suspend themselves, or spin down HDs?

Firewalls are turned off and it still happens

Haven't tried that yet will give it a go.

Worth trying, just in case.

KB925002 4/42007

Search( KB925002 ) - nil hits

Search( 925002 ) - not the right sort of hits

Microsoft( 925002 ) - doesn't look "right" either.

Did you typo the KB number, or swallow a malware look-alike?

--------------- ----- ---- --- -- - - -

Who is General Failure and
why is he reading my disk?

 

[Steve]

Sorry it was a typo, KB925902, but it a null point now

Felt i was going in circles figuring it out, then decided to start from the
beginning setting up the network, checked all users setting and passwords,
all computers on the same workgroup, then used the wizards to setup a
network , then a wireless network.
I am sure I tried this before, but maybe not in that order. All is back to
normal, working as it should.

Not sure what happened, something may have changed without me noticing.

Thanks for the help, sorry if I got over heated.

Steve

cquirke said

For me it is three, 1 desktop, with XP home, one Laptop with Vista home
premium, the third is off most times, it is a XP home lapto[

OK; even the most miserly OS limit should manage that, even with bugs
that see the PC itself as an "incoming connection".

They are cabked and WiFid

OK... which is WiFi'd, and how?

If your WiFi's gaping so that the whole neighborhood is part of your
LAN, then you may have "too many" incoming connects for the OS limit,
and that could blow you off.

Suspect this if "open", WEP, or WPA with < 8 character key.

Not static, my provider does not support that

Not the global IP assigned by the ISP on the WAN side; thinking more
of the internal IP addresses on the LAN side.

yep

Guuud... apparenly this now matters, in Vista.

nope

That makes it easier for me ;-)

what that?

LM hashes are detail within the way that users authenticate when
logging in to a network. It's an old way of holding the password that
has been crackable for a while now, and Vista finally chucks it out.

each couputer has the same accounts, and passwords
OK.


the network comes up only when the XP machine is booted after the Vista
computer, the shares eventually just drop, nothing happens prior to it
happening

Specifically, none of the machines go screen saver and "welcome"
screen, or suspend themselves, or spin down HDs?

Firewalls are turned off and it still happens

Haven't tried that yet will give it a go.

Worth trying, just in case.

KB925002 4/42007

Search( KB925002 ) - nil hits

Search( 925002 ) - not the right sort of hits

Microsoft( 925002 ) - doesn't look "right" either.

Did you typo the KB number, or swallow a malware look-alike?

--------------- ----- ---- --- -- - - -

Who is General Failure and
why is he reading my disk?

--------------- ----- ---- --- -- - - -

 

[cquirke (MVP Windows shell/user)]

Sorry it was a typo, KB925902, but it a null point now

OK, that's the latest ANI patch.

Felt i was going in circles figuring it out, then decided to start from the
beginning setting up the network, checked all users setting and passwords,
all computers on the same workgroup, then used the wizards to setup a
network , then a wireless network.
I am sure I tried this before, but maybe not in that order. All is back to
normal, working as it should.

Not sure what happened, something may have changed without me noticing.

Don't argue with success, just tip-toe away quietly ;-)

------------ ----- ---- --- -- - - - -

Our senses are our UI to reality

 

[Joe Guidera]

I would have said "run, don't walk to the nearest exit and shout in
success - but outside where the computer won't hear you and stop working for
spite"

 

[Steve]

LOL, and that is what happend and the network stopped. Ahhhhhh!! But a
simple cold reboot of computers and it was back.

Hmmm!!! maybe the sleep or hibernation problem that I has been discuussed
here. Trouble bringing the network back on line, or very slow to connect
again.

Other then that all works fine.

Steve