Workgroupt is not accessible

From: Dwaine (anonymous_at_discussions.microsoft.com)
Date: 02/20/04


Date: Fri, 20 Feb 2004 06:42:15 -0800

Hi,

I this is a previous post, but since it is quite old, I
wanted to bring it to the top of the list as I am still
having the problem.

Any suggestions are appreciated.

Thanks,

Dwaine

>>
>>Thank you for your suggestions. Tried those things,
and
>>still having the same problems. IPCONFIG returned a
node
>>type of unknown. The registry had no NodeType nor
>>DhcpNodeType entries, so I created a NodeType and set
the
>>value to 4. The only network connection with the
>>firewall set was the dial-up connection, but still got
>>the same problem when I disabled it. I also tried
using
>>NetBEUI and unbinding IP from file services, but still
>>same issue.
>>
>>What is really wierd is that one XP Pro workstation
works
>>perfectly and can even access the two that have
problems
>>as well as the 98 system. One can access the 98
system,
>>but hangs when trying to print to a printer on it. The
>>third can sometimes see the workgroup and sometimes
gets
>>the error. Even when it accesses the workgroup, it
still
>>cannot see the other workstations.
>>
>>Any other ideas?
>>
>>Thanks,
>>
>>Dwaine
>-----Original Message-----
>In article <1ddd01c3e0e3$d2def150
$a101280a@phx.gbl>, "Dwaine"
><dprice@teknowinc.com> wrote:
>>Hi,
>>
>>I have XP Pro on 3 computers and 98SE on a fourth. I
>>have enabled file sharing on the 98 computer and am
able
>>to access it consistently from one of the XP Pro
>>computers. Another XP Pro computer can see the
workgroup
>>and workgroup computers, but is sporadic in accessing
the
>>other computers' files and/or printers. The third XP
Pro
>>computer is unable to see the workgroup at all and
>>returns "Workgroup name is not accessible. You may not
>>have permission to use this network resource."
>>
>>I have tried using IP and NetBEUI with the same
results.
>>I have verified that all firewalls are turned off and
>>that all machines are able to ping each other and the
>>gateway. I have also run the wizard. I've searched
the
>>knowledge base and have checked all of the suggestions
>>there.
>>
>>Any ideas folks?
>>
>>Thanks,
>>
>>Dwaine
>
>1. Permanently disable XP's built-in Internet Connection
Firewall on
>local area network connections -- it's for use only on a
direct modem
>connection to the Internet. Disable and un-install all
other
>firewalls while troubleshooting. Details here:
>
>Windows XP Internet Connection Firewall
>http://www.practicallynetworked.com/sharing/xp/ic_firewal
l.htm
>
>2. Use only one protocol for File and Printer Sharing.
If the network
>needs more than one protocol, unbind File and Printer
Sharing from all
>but one of them. Details here:
>
>Windows XP Network Protocols
>http://www.practicallynetworked.com/sharing/xp/network_pr
otocols.htm
>
>3. Make sure that NetBIOS over TCP/IP is enabled on all
computers.
>Details here:
>
>Enable NetBIOS Over TCP/IP (NetBT)
>http://www.practicallynetworked.com/sharing/troubleshoot/
netbt.htm
>
>4. Run "ipconfig /all" on XP and look at the "Node Type"
at the
>beginning of the output. If it says "Peer-to-Peer"
(which should
>actually be "Point-to-Point") that's the problem. It
means that the
>computer only uses a WINS server, which isn't available
on a
>peer-to-peer network for NetBIOS name resolution.
>
>If that's the case, run the registry editor, open this
key:
>
> HLM\System\CurrentControlSet\Services\Netbt\Parameters
>
>and delete these values if they're present:
>
> NodeType
> DhcpNodeType
>
>Reboot, then try network access again.
>
>If that doesn't fix it, open that registry key again,
create a DWORD
>value called "NodeType", and set it to 1 for "Broadcast"
or 4 for
>"Mixed".
>
>For details, see these Microsoft Knowledge Base articles:
>
>Default Node Type for Microsoft Clients
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;160177
>
>TCP/IP and NBT Configuration Parameters for Windows XP
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;314053
>--
>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
>.
>
.



Relevant Pages

  • Re: WindowsXP and RISC OS computers
    ... >> - You can however ping Nixiyo from the windows XP machine, ... > workgroup: WORKGROUP ... > Name as M$ calls it, had been changed on the centrex machine. ... > Neither icon appears in My Network Places on the centrex. ...
    (comp.sys.acorn.networking)
  • Re: Simple File Sharing Wont Work
    ... longer access the WORKGROUP. ... I know I'm grasping at straws but how does the network work ... Permanently disable XP's built-in Internet Connection Firewall on ... > Windows XP Internet Connection Firewall ...
    (microsoft.public.windowsxp.network_web)
  • RE: Windows Networking with XP Pro
    ... (Windows XP Pro or Home with SP1 or SP2) ... The computer can ping other computers in the same workgroup. ... Click Start, click Control Panel, and then click Network and Internet ... able to update your profile and access the the partner newsgroups. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Microsoft Home & professional problem
    ... Reconnect all PCs using Windows Network Wizard. ... Windows machines do not need the same Workgroup name to share resources. ... Because one of the computers is XP Pro, disable Simple Sharing from the ...
    (microsoft.public.windowsxp.general)
  • Re: Crossover cable problem
    ... do you have Windows Firewall activated? ... My older pc> default value was 100 mbps, the newer pc was 10 mbps. ... >>>- I've run the network setup wizard numerous times. ... >>>I've found for my config is to specify a workgroup with no ISP ...
    (microsoft.public.windowsxp.network_web)