Browsing workgroup computers

pts.
Tags:
Networking
I am running all xp machines on a peer network and I am having problems getting them to see each other on the network I keep getting the message that the workgroup is not accessible I have the the registry values to make one the master and I continue to have this problem I don't have this problem on my domain networks does anyone have a solution to this dilema Bandit69

Answer Wiki

Thanks. We'll let you know when a new response is added.

Just need to ask a couple simple things to see if they are configured correctly. I assume that you have all the computers configured to use the same workgroup name. When you use the ipconfig /all command, what IP addresses are you getting. Can you ping the other computers on the workgroup? How are all the computers connected?

Check that you have added clients to one work group or connected to same network, its better to add them to one workgroup to access them from one domain.

Discuss This Question: 9  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Bandit69
    I am getting a private IP on bothe computers from the linksys router and I am able to ping all machines
    0 pointsBadges:
    report
  • Hwmcpl
    Are we only talking two machines here and are they running XP Home? Remember there is a peer limit of five or six. I've found in the past - being a smart cookie - that I have only had problems with XP when I set up the network manually. I usually have to go back, remove networking and run the wizard. Once I've done that it all works perfectly. Looks like XP doesn't like smart cookies :D
    0 pointsBadges:
    report
  • J88tru
    Workgroup network connections in XP are a problem in one of my networks, too. What I have found is that XP makes a mess of things by enforcing security and user privileges that were absent in W98 and ME. See below, for new Update issues, and my own questions. I have usually found that by using the Wizard to set up the workgroup on one computer and producing a disk to take to the other machines will cure a lot of problems. Another trick is to force NetBIOS to recognize the other devices in the workgroup, if you are not using a WINS server. You can do this from a command prompt on the client machine, if you know the IP address of the target. Use the command ?nbtstat ?A xxx.xxx.xxx.xxx? (where xxx is the IP address of the target, and the A is case-sensitive). That lists the NetBIOS names in the cache of the target, and sometimes will allow workgroup functions to initiate. When I have done this, the process seems to blink its eyes a couple of times and swallow twice to get going. Almost like it didn?t realize there was something important it was supposed to be doing. You can also use the ?R switch to purge and reload the remote table. I have started using IP adapters for all my remote printers. Makes life a lot easier, especially when you change or rebuild machines. The other trick it to look at ?ipconfig -all?. If the node type is ?Peer-to-Peer? instead of ?Hybrid?, that is the problem, I am told. Only cure is to hack the registry. Let me know if that is what you have and I?ll send the step-by-step. Final answer: I have noticed that XP machines may be blocking normal NetBIOS access, possibly following a windows patch in September or October. This is occurring on both SP1 and SP2 machines. I have actually observed the workgroup ?disappearing? after I surfed to a share on a server-2000 from a new XP/SP1 box. Following that, I got exactly the same error that you did. For several weeks, following a Windows update, I had noticed that the old My Neighborhood ? type display of shares on all the workgroup computers was not working, and did not know what was happening. When I saw XP ?roll up the sidewalks?, I couldn?t believe my eyes. Following that, I have to use W-Explorer, type the share name (ServerAShare) explicitly in the address bar, and respond to the user/password prompt to make it work, even in a share open to ?everybody?. Any responses on my question will be greatly appreciated.
    0 pointsBadges:
    report
  • Ibexinfo
    i also have mistake to connect at my workgroup , I put i can connect to my workgroup and my domain
    0 pointsBadges:
    report
  • Bandit69
    OK I now have 3 machines on the peer and two of them is not having a problem seeing each other but the third which is one of the originals will not see the other two machines so can you give me advice on what else I can do and please send me the registry hack because at this point I'll try anything Thanks Bandit69
    0 pointsBadges:
    report
  • Bandit69
    I Thank you very much for all your help and this is what I did I set up another test network using 1 PC and 2 laptops running XP Settings on PC (Morpheus) Registry: isdomainmaster TRUE mainserverlist Yes Node Type Hybrid Laptop 1 (Thinkpad) Registry: isdomainmaster FALSE mainserverlist Yes Node Type Hybrid Laptop 2 (Inspiron) Registry: isdomainmaster FALSE mainserverlist Yes Node Type unknown When all of the systems are rebooted there is communication, and after about 10 minutes Morpheus can access Inspiron but can't access Thinkpad Inspiron can access Morpheus but can't access Thinkpad and Thinkpad can access Morpheus and Inspiron This is goofy Thanks Again Bandit69
    0 pointsBadges:
    report
  • Microsolve
    Hi Bandit69 Noting the name of your main computer, I wonder if you have considered scanning with Spybot and/or Adaware. If your main computer neme refers to the Morpheus P2P network, and it is connected to it, these networks are notorious for spraying their clients with copious quantities of spyware, causing all sorts of unpredictable behaviour. Dump the spyware or reformat/reinstall WXP on the mani machine after saving all the data you need to keep on one of the machines that can be accessed over the network. Sometimes this is the quickest way! Hope this helps.
    0 pointsBadges:
    report
  • Microsolve
    Hi Bandit69 Noting the name of your main computer, I wonder if you have considered scanning with Spybot and/or Adaware. If your main computer name refers to the Morpheus P2P network, and it is connected to it, these networks are notorious for spraying their clients with copious quantities of spyware, causing all sorts of unpredictable behaviour. Dump the spyware or reformat/reinstall WXP on the mani machine after saving all the data you need to keep on one of the machines that can be accessed over the network. Sometimes this is the quickest way! Hope this helps.
    0 pointsBadges:
    report
  • Mpkn3rd
    I guess we should check the obvious things here as well. What are you calling the workgroup? Are all three computers using the same workgroup name? Can you publish the ipconfig /all results for each of the computers here. You probably should describe the network in greater detail as well. How are the computers getting their IP addresses? If you also check for malware, you may want to get the freeware program called hijackthis and publish the log here as well. That log will determine of there is any malware active on any of the computers as well.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following