How do you delete a workgroup?

  • Thread starter Thread starter JimL
  • Start date Start date
J

JimL

XP Pro SP3 on both machines. Setting up a wireless connection between them.
Both show connections, but I've not gained access yet.

How do you delete a workgroup?

I named the workgroup on my second computer the same as the one on my first
computer thinking that was what was required. But an error line in event
viewer > system said computer 1 rejected the name, so I figure they must
have to be different. I made another workgroup with an appended 2, but now
I can't find a way to get rid of the one without the 2.
 
You don't really delete workgroups, you just rename them... or when on a
network with a domain controller you join the domain. I don't know what
you mean by one machine "rejecting" the workgroup name, all the machines
should be in the same workgroup. Please copy the event from the event
log and paste it here. To copy the event click on the clipboard icon
below the arrows. Edit and remove your personal information from the
event if needed.

John
 
Hi
The Workgroup name must be the same use a name with no spaces and no special
characters and make sure that it is exactly the same for all computers.
Each computer name must be unique. If you have regular home Network do not
use the Network ID button use the change button.
http://www.ezlan.net/network/net-name.jpg
Jack (MS, MVP-Networking).
 
Well, if I were in a networking class I would probably make all F's. I have
tried to "get" networking for 10 or 15 years and it just never makes any
sense to me, so I may have completely misunderstood what the error means.
Here it is:
 
The machine names are simply LAPTOP and LAPTOP2.

The workgroup name I used was my last name.

For all that I'm not even certain "workgroup" is the right word. It is the
name just within My Network Places > Entire Network > Microsoft Windows
Network, and it contains the computer name and icon.
 
The message would usually indicate that the *computers* have identical
names, the computers on a network *must* all have unique names.

I think that you would also get an F in the copying events from Event
Viewer class. You could probably blame the teacher for that because he
probably didn't give a good explanation, maybe the instructions are
better here:
http://www.smartcomputing.com/QABoard/QAMain.aspx?search=fq&fqid=3222856&lnqs=df&qapg=1&guid=

Helpers asking to see errors from the event log usually expect to see
similar to this:

Event Type: Information
Event Source: EventLog
Event Category: None
Event ID: 6005
Date: 12/11/2009
Time: 8:13:22 PM
User: N/A
Computer: ComputerName
Description:
The Event log service was started.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

John
 
Sorry.

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4321
Date: 12/11/2009
Time: 6:40:38 PM
User: N/A
Computer: LAPTOP2
Description:
The name "XXXXXX :1d" could not be registered on the Interface with
IP address 192.168.1.101. The machine with the IP address 192.168.1.100 did
not allow the name to be claimed by this machine.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 04 00 56 00 ......V.
0008: 00 00 00 00 e1 10 00 c0 ....á..À
0010: 01 01 00 00 01 00 00 c0 .......À
0018: 13 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........


John John - MVP said:
The message would usually indicate that the *computers* have identical
names, the computers on a network *must* all have unique names.

LAPTOP and LAPTOP2
 
How are the machines obtaining their IP addresses?

At a command prompt issue the ipconfig /all command and post the results
from both machines.

John
 
John John - MVP said:
How are the machines obtaining their IP addresses?

At a command prompt issue the ipconfig /all command and post the results
from both machines.



Here are the results. I recognize bits and pieces, but grasp nothing of the
relation between them.


Windows IP Configuration

Host Name . . . . . . . . . . . . : LAPTOP
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.tn.comcast.net.

Ethernet adapter Wireless Network Connection 2:

Connection-specific DNS Suffix . : hsd1.tn.comcast.net.
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG
Network
Connection
Physical Address. . . . . . . . . : 00-0E-35-52-88-AA
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::20e:35ff:fe52:88aa%4
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
68.87.68.166
68.87.74.166
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Lease Obtained. . . . . . . . . . : Saturday, December 12, 2009
1:22:28
PM
Lease Expires . . . . . . . . . . : Sunday, December 13, 2009
1:22:28 PM


Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling
Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%5
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled


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


Windows IP Configuration

Host Name . . . . . . . . . . . . : LAPTOP2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.tn.comcast.net.

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : hsd1.tn.comcast.net.
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG
Networ
k Connection
Physical Address. . . . . . . . . : 00-19-D2-9F-05-90
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
68.87.68.166
68.87.74.166
Lease Obtained. . . . . . . . . . : Saturday, December 12, 2009
3:00:29
PM
Lease Expires . . . . . . . . . . : Sunday, December 13, 2009
3:00:29 PM


Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network
Connect
ion
Physical Address. . . . . . . . . : 00-16-41-E1-7A-A6
 
JimL said:
Here are the results. I recognize bits and pieces, but grasp nothing of the
relation between them.


I'm not sure what to make of the connection on LAPTOP that shows two IP
addresses on 00-0E-35-52-88-AA:

Physical Address. . . . . . . . . : 00-0E-35-52-88-AA
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::20e:35ff:fe52:88aa%4

....

Maybe someone else reading here knows what the heck is going on with that.

John
 
Back
Top