Unable to access network

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have, what I hope, is a relatively easy netowking problem. I have a simple
Workgroup set up. 1 PC runs WinXP Pro SP2 and the other runs Win200 PRO SP4.
I'm able to browse the network from the XP Pro PC, but from the Win2K PC, I
can only see the workgroup name. If I click on it, I get the "unable to
access the network" error. I'm able to ping both PC's by computer name and IP
address. If I type the WinXP Pro's computer name or IP address into the run
command, nothing opens. If I type the Win2K PC's IP address or computer name
into the run command, I get a list of the shared resources on the PC. I do
both of these from the Win2K PC. I have read several knowledge base articles,
but have not been able to resolve the issue. I also dont' know, exactly when
this problem arose. I would like to be able to browse the network and share
resources from both PCs again.

Any insight would be greatly appreciated.
 
christopher robin said:
I have, what I hope, is a relatively easy netowking problem. I have a simple
Workgroup set up. 1 PC runs WinXP Pro SP2 and the other runs Win200 PRO SP4.
I'm able to browse the network from the XP Pro PC, but from the Win2K PC, I
can only see the workgroup name. If I click on it, I get the "unable to
access the network" error. I'm able to ping both PC's by computer name and IP
address. If I type the WinXP Pro's computer name or IP address into the run
command, nothing opens. If I type the Win2K PC's IP address or computer name
into the run command, I get a list of the shared resources on the PC. I do
both of these from the Win2K PC. I have read several knowledge base articles,
but have not been able to resolve the issue. I also dont' know, exactly when
this problem arose. I would like to be able to browse the network and share
resources from both PCs again.

Any insight would be greatly appreciated.
Click to expand...

Start with some basic diagnostics:
1. Turn off your WinXP firewall.
2. Turn off any other firewall, especially those that are integrated with
virus scanners.
3. Start a Command Prompt on both PCs.
4. Find out the IP addresses of both PCs. IPConfig.exe will tell you.
5. Ping each PC from the other PC.
6. Type this command on the Win2000 PC:
net use x: \\NameOfWinXP-PC\NameOfShare

Report the results in your reply!
 
in message
:I have, what I hope, is a relatively easy netowking problem. I have a
simple
: Workgroup set up. 1 PC runs WinXP Pro SP2 and the other runs Win200 PRO
SP4.
: I'm able to browse the network from the XP Pro PC, but from the Win2K PC,
I
: can only see the workgroup name. If I click on it, I get the "unable to
: access the network" error. I'm able to ping both PC's by computer name and
IP
: address. If I type the WinXP Pro's computer name or IP address into the
run
: command, nothing opens. If I type the Win2K PC's IP address or computer
name
: into the run command, I get a list of the shared resources on the PC. I do
: both of these from the Win2K PC. I have read several knowledge base
articles,
: but have not been able to resolve the issue. I also dont' know, exactly
when
: this problem arose. I would like to be able to browse the network and
share
: resources from both PCs again.
:
: Any insight would be greatly appreciated.

Have you looked here:
http://support.microsoft.com/?id=318030

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
FAQ W2K/2K3 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;291382
 
Thank you for the information, but that is one of the KB Articles I've read
already, and netbios over TCP/IP is enabled, and the Computer Browser Service
is running.
 
Thank you for the reply. The requested information if provided below.

Pegasus (MVP) said:
Start with some basic diagnostics:
1. Turn off your WinXP firewall.
Click to expand...
I don't use WinXP Firewall, and the serive is set to manual.
2. Turn off any other firewall, especially those that are integrated with
virus scanners.
Click to expand...
I use Norton AntiVirus and Firewall, and have disabled both for testing.
3. Start a Command Prompt on both PCs.
4. Find out the IP addresses of both PCs. IPConfig.exe will tell you.
Click to expand...
WinXP results of Ipconfig:

Windows IP Configuration

Ethernet adapter Q-Continuum:

Connection-specific DNS Suffix . : earthlink.net
IP Address. . . . . . . . . . . . : 192.168.69.182
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter Comcast Cable:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

Ethernet adapter Earthlink DSL:

Connection-specific DNS Suffix . : earthlink.net
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

Win2K Results of IPConfig:

Windows 2000 IP Configuration

Ethernet adapter Comcast Broadband:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.1.150
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

Ethernet adapter Earthlink DSL:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.0.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

Ethernet adapter Q-Continuum:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.69.90
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
5. Ping each PC from the other PC.
Click to expand...
Pinging Win2K PC from WinXP PC:

Pinging CHRISFO-JP [192.168.69.90] with 32 bytes of data:

Reply from 192.168.69.90: bytes=32 time<1ms TTL=128
Reply from 192.168.69.90: bytes=32 time<1ms TTL=128
Reply from 192.168.69.90: bytes=32 time<1ms TTL=128
Reply from 192.168.69.90: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.69.90:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging WinXP PC from Win2K PC:

Pinging SHINOBI [192.168.69.182] with 32 bytes of data:

Reply from 192.168.69.182: bytes=32 time<10ms TTL=64
Reply from 192.168.69.182: bytes=32 time<10ms TTL=64
Reply from 192.168.69.182: bytes=32 time<10ms TTL=64
Reply from 192.168.69.182: bytes=32 time<10ms TTL=64

Ping statistics for 192.168.69.182:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
6. Type this command on the Win2000 PC:
net use x: \\NameOfWinXP-PC\NameOfShare
Click to expand...

I typed: net use x: \\Shinobi\Strategies, and the command completed
successfully. I was able to access the X Drive and view the information.

I then enabled my firewall, and again, I was unable to access the share.
It's the firewall. UGH!

Thanks for all the insight.
 
Okay, after I typed in my reply, the newsgroup gave me an error and said that
my post was not received. I have figured out, though, what was causing the
problem. Norton Firewall was blocking Win2K's access to the local network.
I've added the range of IP address in the "allow" list for Norton Firewall,
and now it's working as it should.

Thanks for the insight.
 
UGH! After typing in my response, the newsgroup server didn't accept my
post. I have determined, though, through the process of answering your
queries that Norton Firewall was blocking acces to the local network. I've
added my LAN's subnet to the "allow" list in Norton Firewall, and I'm now
able to browse the network and use the resources on my WinXP system.

Thanks for the help.
 
Back
Top