workgroup reverts to MSHOME

No, it doesn't make it impossible, but it's very
disconcerting for the user to have his environment suddenly
disappear!

>-----Original Message-----
>In article <026701c38dcd$f8a12bb0$a401280a@phx.gbl>,

"Garry Allen"

><gallen.dbmc@kingston.net> wrote:

>>The other day I went to a client's site because one of
>>their machines running XP Home could not access the other
>>machines on the network. I found that the workgroup had
>>changed to MSHOME. I assumed that they had done something
>>accidentally, reset it to the proper Workgroup and
>>everything was fine.
>>Today I doscovered that the same thing happened on an XP
>>Hoem machine in our own office. Has some WinXP update
>>caused this?

>
>I'm sorry, but I don't know why the workgroup name is

reverting.

>However, that shouldn't stop computers from accessing each

other.

>Windows networking supports multiple workgroups, and

computers in any

>workgroup can access computers in any other workgroup.
>--
>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
>.
>

I suppose you could try configuring and then saving a restore point.
Dave
"Garry Allen" <gallen.dbmc@kingston.net> wrote in message
news:0a1d01c38f02$fb536900$a401280a@phx.gbl...

> No, it doesn't make it impossible, but it's very
> disconcerting for the user to have his environment suddenly
> disappear!
>

> >-----Original Message-----
> >In article <026701c38dcd$f8a12bb0$a401280a@phx.gbl>,

> "Garry Allen"

> ><gallen.dbmc@kingston.net> wrote:

> >>The other day I went to a client's site because one of
> >>their machines running XP Home could not access the other
> >>machines on the network. I found that the workgroup had
> >>changed to MSHOME. I assumed that they had done something
> >>accidentally, reset it to the proper Workgroup and
> >>everything was fine.
> >>Today I doscovered that the same thing happened on an XP
> >>Hoem machine in our own office. Has some WinXP update
> >>caused this?

> >
> >I'm sorry, but I don't know why the workgroup name is

> reverting.

> >However, that shouldn't stop computers from accessing each

> other.

> >Windows networking supports multiple workgroups, and

> computers in any

> >workgroup can access computers in any other workgroup.
> >--
> >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
> >.
> >

I had the same thing happen to my client as well. (that's why I'm here today).

My client is very unlikely to make changes to their PC's. One PC which was functioning very nicely last week, suddenly could not access the network resources at all (workgroup only, ME, XPhome), nor could it be accessed FROM the network. Sadly, this was the PC containing all of the office files so business stopped.

After quick inspection, I found the same problem Garry seems to have had; the PC had been removed from the workgroup and added to the "MSHOME" workgroup. I changed the workgroup back, rebooted and voila.. it worked again. (But do you think my client believes that I didn't screw it up in the first place?)

I see a LOT of people with this problem on various newsgroups and perhaps they are not explaining it well enough because some of the MVP answers are so far from the question. We need a real answer I think. WHAT is causing all of these PC's to switch workgroups to "MSHOME" with no provocation from anyone?

If it helps, I also noticed that the built-in firewall protection was on. I know that it was off during my last visit a week ago.

All my users do without my consent is allow all recommended updates from windowsupdate... I insist that they do the updates the minute they arrive.

I tend to think it is an update that went out that is causing some of these incidents.

James


"Steve Winograd [MVP]" <winograd@pobox.com> wrote in message news:g1q8ov4mkd4745qt3uhiksfp9thn7keip8@4ax.com...

> In article <026701c38dcd$f8a12bb0$a401280a@phx.gbl>, "Garry Allen"
> <gallen.dbmc@kingston.net> wrote:

> >The other day I went to a client's site because one of
> >their machines running XP Home could not access the other
> >machines on the network. I found that the workgroup had
> >changed to MSHOME. I assumed that they had done something
> >accidentally, reset it to the proper Workgroup and
> >everything was fine.
> >Today I doscovered that the same thing happened on an XP
> >Hoem machine in our own office. Has some WinXP update
> >caused this?

>
> I'm sorry, but I don't know why the workgroup name is reverting.
> However, that shouldn't stop computers from accessing each other.
> Windows networking supports multiple workgroups, and computers in any
> workgroup can access computers in any other workgroup.
> --
> 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

In article <#winpwQoDHA.2820@TK2MSFTNGP10.phx.gbl>, "James White"
<jwhite@ctbr.org> wrote:

>I had the same thing happen to my client as well. (that's why I'm here today).
>
>My client is very unlikely to make changes to their PC's. One PC which was functioning very nicely last week, suddenly could not access the network resources at all (workgroup only, ME, XPhome), nor could it be accessed FROM the network. Sadly, this was the PC containing all of the office files so business stopped.
>
>After quick inspection, I found the same problem Garry seems to have had; the PC had been removed from the workgroup and added to the "MSHOME" workgroup. I changed the workgroup back, rebooted and voila.. it worked again. (But do you think my client believes that I didn't screw it up in the first place?)
>
>I see a LOT of people with this problem on various newsgroups and perhaps they are not explaining it well enough because some of the MVP answers are so far from the question. We need a real answer I think. WHAT is causing all of these PC's to switch workgroups to "MSHOME" with no provocation from anyone?
>
>If it helps, I also noticed that the built-in firewall protection was on. I know that it was off during my last visit a week ago.
>
>All my users do without my consent is allow all recommended updates from windowsupdate... I insist that they do the updates the minute they arrive.
>
>I tend to think it is an update that went out that is causing some of these incidents.
>
>James

Running the Network Setup Wizard and accepting its default settings
will change the workgroup name to MSHOME.
--
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