Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 668
  • Last Modified:

Workgroup MSHOME split into two with one computer in both

I started working on a network with 10 computers - including my own XP laptop.
All of the computers are set for DHCP.
There is a single DSL modem feeding a single 16-port switch.
The switch goes to a patch panel which feeds all the ethernet jacks in the small building.

Originally, there were two workgroups: MSHOME and OFFICE and I found one computer with WORKGROUP.
I changed them all to MSHOME because the critical computers were communicating on that workgroup - so I figured to join the others into that one.
Most of the computers are XP.  One is 98 and a new one is Vista Business.

The Vista machine doesn't see any other - just itself in the MSHOME workgroup.
What I shall call MSHOME #1, has 6 computers including the Vista computer and a computer I shall call COMMON1.
What I shall call MSHOME #2, has 5 computers including COMMON1
COMMON1 shows all of the computers.

I have been patient, as I have advised others here.  I shut down all the computers and selectively brought them back up.  This had no affect.

I have to go back tomorrow to resolve this.  It has me stumped for now.

0
Fred Marshall
Asked:
Fred Marshall
  • 3
1 Solution
 
Fred MarshallAuthor Commented:
One can ping across the whole network it appears.
on MSHOME #2 nbtstat -n yields no names in the list.
0
 
Fred MarshallAuthor Commented:
The computers are all in the same subnet - DHCP from a single router.
Here is the ipconfig/all from the Vista machine:
Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : domain_not_set.invalid
   Description . . . . . . . . . . . : Intel(R) 82562V-2 10/100 Network Connecti
on
   Physical Address. . . . . . . . . : 00-21-9B-08-31-64
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.111(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Friday, October 10, 2008 9:35:31 AM
   Lease Expires . . . . . . . . . . : Saturday, October 11, 2008 9:35:32 AM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 216.177.224.9
                                       216.177.225.9
                                       192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled
0
 
Fred MarshallAuthor Commented:
I found the culprit(s):

1) NWLink protocols were installed on all the computers in one group.

2) Microsoft Client for Networking was installed but not checked.

3) Windows File and Print Sharing was installed but not checked.

Solution:
Remove Netware protocols on all computers.
Turn on Microsoft Client for Networking and Windows File and Print Sharing
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now