Probably it's Samba's fault (or it's cache). The Workgroup
name was changed, not the SSID.
This is my original settings (I also did some troubleshooting):
- All machines with all patches (of course ^.^)
- MBNU disabled (not in startup group)
- Workgroup name COMPANY_NAME
- I have XP, Win 9x, and debian (linux) boxes running
- One of the debian boxes is running Samba (file and
printer server for Windows)
- The Samba box is set to Workgroup COMPANY_NAME
- The Samba box is the master browser for the LAN
On the wired machine where the workgroup name changed:
- No software firewall or ICF running at time of upgrade
and after the reboot
- File and Printer Sharing disabled on the Local Area
Connection Properties dialog box
In addition:
- The Samba box cached MSHOME as additional Workgroup
name and was broadcasting it!!
Does the install or the MBNU looks up available workgroups
on the LAN, and tries to *assign* a workgroup or *fix* the
workgroup name? In that case it didn't pick the right
workgroup name.
The thing is that I have the same settings, but with ICF
enabled and UPNP and DHCP client services disabled on a
wireless PC and it did not change the workgroup. So the
wifi card, ICF, UPNP, and/or DHCP client must have affected
the behavior.
>-----Original Message-----
>Do you mean the Wireless network name (SSID) of the MN-700
changed to MSHOME
>or the Workgroup name of the PC?
>
>The Update Wizard does not have the ability to change the
Workgroup name.
>Restoring to Factory Defaults on the MN-700 will change
the SSID to MSHOME.
>
>--
>Neel Malik
>Program Manager
>Microsoft Corporation
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>
>"lilo" <(E-Mail Removed)> wrote in message
>news:23dc01c47025$c21392a0$(E-Mail Removed)...
>> I installed the upgrade yesterday, and after I rebooted
>> this morning my workgroup name changed to MSHOME. (And yes,
>> I installed the upgrade and not the CD install)
>>
>> Anyone having same behavior?
>>
>
>
>.
>
|