Re: Workgroup

From: Cheng (acheng_at_kemaconsulting.com)
Date: 02/04/04


Date: Wed, 4 Feb 2004 15:47:42 -0800

Steve,

Thanks for your posted information. I find it very useful.

I have one XP Home used as a file server and 5 other PCs
(2 PCs run Win98, 3 PCs run XP home) on a 100M ethernet.
Occasionally (nearly every day) when I transfer (either
way) a folder/file between a PC and the file server, it
does not respond for 30 to 50 seconds before the transfer
takes place. Sometime a small file transfer (200K) takes
minutes or never completed. This happens to Win98 and
WinXP PCs. If I restart my my PC (not the server), it
becomes good for awhile and falls back to the same problem
later.

I did "ipconfig /all". It reports "NodeType: unknown".
The server has a fixed IP address. I guess that could be
the reason it does not report "DHCPNodeType".

I'd appreciate if you give me some pointers to resolve
this problem.

Thanks.
Cheng
>-----Original Message-----
>In article <90b101c3ea91$ad6068c0
$a301280a@phx.gbl>, "Alex"
><ajbtlk@hotmail.com> wrote:
>>I have a pc running xp home edition that would not see
the
>>work group. Four other computers running xp
professional
>>work fine. I upgraded the xp home to xp professional
and
>>it still will not see any computers in the workgroup.
All
>>protocols are installed, it can access the internet,
>>everything is fine except for that. Any suggestions
will
>>help
>
>A key to Windows networking is to use the same, single
network
>protocol for file and printer sharing on all computers.
Using more
>than one protocol can make the network unreliable,
especially when XP
>is involved. Remove NetBEUI and IPX/SPX from all
computers unless you
>have a specific need for them. If you use one of them
for file and
>printer sharing, un-bind sharing from the other
protocols. I've
>written a web page with details:
>
>Windows XP Network Protocols
>http://www.practicallynetworked.com/sharing/xp/network_pro
tocols.htm
>
>If that doesn't solve the problem, try these tips:
>
>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_firewall
.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_pro
tocols.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/n
etbt.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: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: random lockouts
    ... >> I've got a network with several Windows 2000 Servers and ... >> about 150 Windows 98 clients. ... >This problem occurs because the Windows 2000-based server ... >because the session that is reused is against a DFS ...
    (microsoft.public.win2000.security)
  • Questions Relating to Administering Windows 2000 Server
    ... installed the network client on the target computer. ... Sarah has been attempting to install Windows 2000 ... Server for two days. ... Sarah has checked the cables and hard drives. ...
    (microsoft.public.cert.exam.mcse)
  • Questions Relating to Administering Windows 2000 Server
    ... installed the network client on the target computer. ... Sarah has been attempting to install Windows 2000 ... Server for two days. ... Sarah has checked the cables and hard drives. ...
    (microsoft.public.cert.exam.mcse)

Quantcast