In article <360601c3e20d$748c2660$(E-Mail Removed)>, "Carolyn"
<(E-Mail Removed)> wrote:
>have a customer. was running two win98 machines connected
>with a hub for about 3 years. now introduce a xp machine
>to replace one of the 98 machines. i have having severe
>connectivity problems. i finally can connect and then in
>the morning it's unable to connect.
>
>decided to try the following: i reinstall winxp and added
>netbui on the xp machine. i have a network disk created
>and after attempting to load on the 98 machine it responds
>that the disk was unable to load because there was no
>networking hardware. i am able to ping only each card,
>not each other. the other day they were connected and
>working fine. this particular customer does have alot of
>fluroscent lighting and i've heard that could cause some
>problems, but why start now.
>
>the windows 98 machine sees itself. the xp machine sees
>itself in the network neightborhood. there is an error
>message that one of the mapped drives on the xp machine is
>not connected,
>
>carolyn
There's no reason to install NetBEUI on XP unless the existing network
already uses NetBEUI for file and printer sharing. XP's Network Setup
Wizard configures computers to use TCP/IP, not NetBEUI.
The Network Setup Wizard sometimes fails to recognize an installed
network adapter. That's probably because of an error in the driver
program for the network adapter. However, it's never necessary to run
the Wizard. You can make all the network settings manually.
I've written a web site that should help you get everything working:
Adding Windows XP to an Existing Network
http://www.practicallynetworked.com/...g/xp/addxp.htm
If that doesn't do the job, 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/...c_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/..._protocols.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/...hoot/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\Parame ters
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...b;en-us;160177
TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/default...b;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 - Windows Networking
http://mvp.support.microsoft.com
Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm
Similar Threads
Linear Mode
