XP & 98 network problem

  • Thread starter Thread starter Sam
  • Start date Start date
S

Sam

I have two machine running XP and on 98 machine. The XP
machines don't have a problem, yet I'm having problems
with the 98 machine. I know it's not a hardware problem
with my network card because I can ping 127.0.0.1 just
fine.

The problem is when I try to access the XP machine, I get
access denied error. File and Printer sharing is enabled
and I am clueless to what the problem might be.
 
"Sam" said:
I have two machine running XP and on 98 machine. The XP
machines don't have a problem, yet I'm having problems
with the 98 machine. I know it's not a hardware problem
with my network card because I can ping 127.0.0.1 just
fine.
Click to expand...

That doesn't tell you anything about the network card -- it just tells
you that the TCP/IP protocol is installed and working. You can even
ping 127.0.0.1 on a computer that doesn't have a network card.
The problem is when I try to access the XP machine, I get
access denied error. File and Printer sharing is enabled
and I am clueless to what the problem might be.
Click to expand...

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_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/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
 
"Sam" said:
Thanks so much Steve.

Hey, can you explain this in the MS KB Article because
I'm confused.

http://support.microsoft.com/default.aspx?scid=kb;en-us;115492
Click to expand...

That article gives tips for troubleshooting problems connecting to an
SMTP server to send E-mail. I don't think that it applies to your
situation, because this appears at the end of the article:

The information in this article applies to:

Microsoft Mail Gateway to SMTP 3.0
--
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
 
Thanks. My problem is fixed.

I know this isn't a real problem nor it is accurate.

Let's say it was a problem with TCP/IP and I resintalled
it because it was corrupted, yet I still cannot ping the
loopback address. I was told if that didn't work then
replace the network card. Is this only a myth?



-----Original Message-----
Click to expand...
 
"Sam" said:
Thanks. My problem is fixed.

I know this isn't a real problem nor it is accurate.

Let's say it was a problem with TCP/IP and I resintalled
it because it was corrupted, yet I still cannot ping the
loopback address. I was told if that didn't work then
replace the network card. Is this only a myth?
Click to expand...

That's a myth, as I explain on this web page:

Steve Winograd's Networking Myths
http://www.bcmaven.com/networking/myths.htm

The most likely reason that you can't ping the loopback address is an
improperly configured firewall program. Un-install (don't just
disable) ZoneAlarm, Norton Internet Security, etc, go to Start | Run |
Msconfig and disable any firewall remnants, reboot, and try again.
--
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
 
Back
Top