Re: Workgroup is not accessible.

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


Date: Wed, 11 Feb 2004 06:07:02 -0800

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: Still cant connect to RWW or OWA remotely
    ... No, I don't have a 3rd party firewall, and it's a pretty plain vanilla WinXP ... Connected to the network like the other workstations, ... I could go to any workstation and connect to them just fine. ... match the broadband connection, the two NIC firewall, the remote ...
    (microsoft.public.windows.server.sbs)
  • RE: Serious Security Issue in Windows XP SP2s Firewall
    ... file and printer sharing is available for network login from any network (I ... Internet Connection Sharing of the PC has to be disabled." ... Serious Security Issue in Windows XP SP2's Firewall ...
    (Focus-Microsoft)
  • Re: Can not find other devices on Network
    ... The link you specified shows the workgroup the way it displays in XP. ... Network traffic as trusted. ... start by running the Network Setup Wizard on all machines (see ... by 1) a misconfigured firewall or overlooked firewall (including a stateful ...
    (microsoft.public.windows.vista.networking_sharing)
  • Re: Can not find other devices on Network
    ... The link you specified shows the workgroup the way it displays in XP. ... Network traffic as trusted. ... start by running the Network Setup Wizard on all machines (see ... by 1) a misconfigured firewall or overlooked firewall (including a stateful ...
    (microsoft.public.windows.vista.networking_sharing)
  • RE: Lost Internet Connectivity
    ... use network diagnostic tools, i.e. ipconfig, ping, etc. ... Firewall, McAfee Personal Firewall, VS, two-PC network, Motorola modem, ... PCI 10/100 Ethernet Connection. ... Windows Firewall/ICS Service not running, ...
    (microsoft.public.windowsxp.network_web)