I have two wireless-enabled notebooks both running XP Home and both able to
access the Internet fine. I have followed all the instructions for file and
printer sharing and run the Network troubleshooter, etc. I have also enabled
NetBIOS over TCP/IP on both computers. However the computers cannot access
each other's SharedDocs. In fact computer B's own SharedDocs do not even
appear in My Network Places, whereas computer A's appear in its MNP. Computer
B can ping successfully computer A, but not vice versa. It all seemed to work
OK (although I didn't have much call to rely on shared files) until a couple
of weeks ago when I tried to share a printer plugged into computer A from
computer B.

I would be most grateful for any further ideas - am I missing something?

On Fri, 10 Jun 2005 20:27:01 -0700, slowey <slo***@discussions.microsoft.com>
wrote:

With two wireless servers, and the MNP discrepancies, I'd bet you have a browser
problem.
<http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html>

The ping problem may indicate a firewall malfunction too.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>

Thanks for the rapid reply, Chuck!

I have installed browstat on computer B and also temporarily disabled Norton
Internet Security (which, surprise surprise I had installed on that computer
about two weeks ago when the problems started). Computer B now has access to
computer A's shareddocs, but not yet vice versa (restarting both computers
did not help). I will set it up properly later, but at least this
demonstrated the firewall was at least part of the problem.

After running Browstat on computer B, there appear to be two problems
compared to the example on your very helpful webpage about Browstat. Firstly,
it "Could not connect to registry, error = 53" and was "Unable to determine
build of browser master: 53". Secondly, it retrieved only one backup server
from Computer A, namely Computer A.

Not sure what this means I should do, and again would be most grateful for
your sage advice, Chuck.

many thanks

Show quoteHide quote

On Sat, 11 Jun 2005 04:30:03 -0700, slowey <slo***@discussions.microsoft.com>
wrote:

Show quoteHide quoteAn "error 53" is "name not found".  That means that your computer can't resolve
the name of the browser server into an address.  This is generally caused by a
firewall blocking the name resolution process, or an invalid Node Type for name
resolution.

Run "ipconfig /all" on both computers, and see if there's a problem there.
<http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html>

Did you examine the browstat output per my instructions, and find no problems
other than the "error 53" (which is simply a symptom there)?

If no clues are offered by either "browstat status" or "ipconfig /all", then
you'll have to either enable Norton Personal Firewall and properly configure it,
or un install it totally, per detailed procedures (not just the un install
wizard) provided by Symantec.  NPF, like many Symantec products, is known for
not reacting properly when deactivated, nor can it be reliably un installed
using only its un install wizard.

Hi Chuck

Thanks for your help, but I'm still not any further advanced. I think I have
now tried all the things on your very helpful site, including the browstat
page and the network troubleshooting page. I have checked the Norton
documentation and uninstalling the NIS from Add/Remove Programs is sufficient
for a complete uninstall. 'A' now has NIS 2005 installed with the Personal
Firewall running and the DNS server and 'B' listed in the trusted area. 'B'
now just has Windows Firewall on. Both computers' firewalls have file sharing
enabled in the relevant ways. The browstat output today looks fine for 'B'
now but the error:53 problem is now with 'A'. Another potential problem is
that ipconfig on 'B' revealed an unknown node type, and inserting the
EnableProxy line in regedit did not rectify this.

So, I am at a loss, and feel quite out of my depth here.

I have pasted the ipconfig and browstat outputs from each computer below,
and would be most grateful for any further advice you (or anyone else) are
able to offer.

Ipconfig ('A')

Windows IP Configuration        Host Name . . . . . . . . . . . . :
OLDCOMPUTER        Primary Dns Suffix  . . . . . . . :         Node Type . .
.. . . . . . . . . . : Hybrid        IP Routing Enabled. . . . . . . . : No   
    WINS Proxy Enabled. . . . . . . . : NoEthernet adapter Wireless Network
Connection:        Connection-specific DNS Suffix  . :         Description .
.. . . . . . . . . . : LAN-Express IEEE 802.11 PCI Adapter        Physical
Address. . . . . . . . . : 00-02-8A-98-F1-B5        Dhcp Enabled. . . . . . .
.. . . . : Yes        Autoconfiguration Enabled . . . . : Yes        IP
Address. . . . . . . . . . . . : 192.168.0.100        Subnet Mask . . . . . .
.. . . . . : 255.255.255.0        Default Gateway . . . . . . . . . :
192.168.0.1        DHCP Server . . . . . . . . . . . : 192.168.0.1        DNS
Servers . . . . . . . . . . . : 192.168.0.1        Lease Obtained. . . . . .
.. . . . : Sunday, 12 June 2005 11:23:30 AM        Lease Expires . . . . . . .
.. . . : Sunday, 19 June 2005 11:23:30 AM

Browstat ('A')

Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{3FCA99BF-F27B-451F-B6E8-27B63C23199A}
    Browsing is active on domain.
    Master browser name is: NEWCOMPUTER
Could not connect to registry, error = 53        Unable to determine build
of browser master: 53
    \\\\NEWCOMPUTER   .  Version:05.01  Flags: 51203 NT POTENTIAL MASTER
    1 backup servers retrieved from master NEWCOMPUTER
        \\NEWCOMPUTER
    Unable to retrieve server list from NEWCOMPUTER: 64

Ipconfig ('B')

Windows IP Configuration        Host Name . . . . . . . . . . . . :
NEWCOMPUTER        Primary Dns Suffix  . . . . . . . :         Node Type . .
.. . . . . . . . . . : Unknown        IP Routing Enabled. . . . . . . . : No  
     WINS Proxy Enabled. . . . . . . . : NoEthernet adapter Wireless Network
Connection:        Connection-specific DNS Suffix  . :         Description .
.. . . . . . . . . . : Intel(R) PRO/Wireless 2200BG Network Connection       
Physical Address. . . . . . . . . : 00-0E-35-4C-55-42        Dhcp Enabled. .
.. . . . . . . . . : Yes        Autoconfiguration Enabled . . . . : Yes       
IP Address. . . . . . . . . . . . : 192.168.0.101        Subnet Mask . . . .
.. . . . . . . : 255.255.255.0        Default Gateway . . . . . . . . . :
192.168.0.1        DHCP Server . . . . . . . . . . . : 192.168.0.1        DNS
Servers . . . . . . . . . . . : 192.168.0.1        Lease Obtained. . . . . .
.. . . . : Sunday, 12 June 2005 11:22:50 AM        Lease Expires . . . . . . .
.. . . : Sunday, 19 June 2005 11:22:50 AM

browstat ('B')

Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{86F61F2B-CC7B-4673-A416-A97C043AE6D4}
    Browsing is active on domain.
    Master browser name is: NEWCOMPUTER
        Master browser is running build 2600
    1 backup servers retrieved from master NEWCOMPUTER
        \\NEWCOMPUTER
    There are 2 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{86F61F2B-CC7B-4673-A416-A97C043AE6D4}
    There are 1 domains in domain MSHOME on transport
\Device\NetBT_Tcpip_{86F61F2B-CC7B-4673-A416-A97C043AE6D4}

many thanks
Show quoteHide quote

On Sat, 11 Jun 2005 19:46:02 -0700, slowey <slo***@discussions.microsoft.com>
wrote:

Show quoteHide quoteSo from which computer did you un install NIS?  Computer B looks clean now.  Try
doing the same to Computer A.  Also check Computer A for a corrupt LSP /
Winsock.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>

The Node Type Unknown, as far as I know, does not cause a problem, nor is it
necessarily indicative of one.  My computers have run fine for a couple years as
Node Type Unknown; having read the article, I have considered fixing the
situation per the article ""Ipconfig /All" Command Shows the Node Type as
Unknown", but not with any amount of haste.

Hi Chuck

As suggested, I have uninstalled NIS from computer 'A' and checked for a
corrupt Winsock using netdiag but it passed all the tests. I reinstalled it
anyway using "netsh winsock reset" and restarted. Unfortunately I still have
an error 53 in computer A's browstat output. I have redone browstat and
pasted the output below. Any further ideas? :)

'A'

Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{3FCA99BF-F27B-451F-B6E8-27B63C23199A}
    Browsing is active on domain.
    Master browser name is: NEWCOMPUTER
Could not connect to registry, error = 53        Unable to determine build
of browser master: 53
    \\\\NEWCOMPUTER   .  Version:05.01  Flags: 51203 NT POTENTIAL MASTER
    1 backup servers retrieved from master NEWCOMPUTER
        \\NEWCOMPUTER
    There are 2 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{3FCA99BF-F27B-451F-B6E8-27B63C23199A}
    Unable to retrieve server list from NEWCOMPUTER: 64

'B'

Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{86F61F2B-CC7B-4673-A416-A97C043AE6D4}
    Browsing is active on domain.
    Master browser name is: NEWCOMPUTER
        Master browser is running build 2600
    1 backup servers retrieved from master NEWCOMPUTER
        \\NEWCOMPUTER
    There are 2 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{86F61F2B-CC7B-4673-A416-A97C043AE6D4}
    There are 1 domains in domain MSHOME on transport
\Device\NetBT_Tcpip_{86F61F2B-CC7B-4673-A416-A97C043AE6D4}

many thanks!

Show quoteHide quote

On Sat, 11 Jun 2005 22:42:02 -0700, slowey <slo***@discussions.microsoft.com>
wrote:

Show quoteHide quoteWhen did you do the latest browstats - with NPF un installed from OldComputer?
Or after?  Or before?

Look at the difference:

From earlier today:
Browstat ('A')

Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{3FCA99BF-F27B-451F-B6E8-27B63C23199A}
    Browsing is active on domain.
    Master browser name is: NEWCOMPUTER
Could not connect to registry, error = 53        Unable to determine build
of browser master: 53
    \\\\NEWCOMPUTER   .  Version:05.01  Flags: 51203 NT POTENTIAL MASTER
    1 backup servers retrieved from master NEWCOMPUTER
        \\NEWCOMPUTER
    Unable to retrieve server list from NEWCOMPUTER: 64

Most recently:
'A'

Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{3FCA99BF-F27B-451F-B6E8-27B63C23199A}
    Browsing is active on domain.
    Master browser name is: NEWCOMPUTER
Could not connect to registry, error = 53        Unable to determine build
of browser master: 53
    \\\\NEWCOMPUTER   .  Version:05.01  Flags: 51203 NT POTENTIAL MASTER
    1 backup servers retrieved from master NEWCOMPUTER
        \\NEWCOMPUTER
    There are 2 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{3FCA99BF-F27B-451F-B6E8-27B63C23199A}
    Unable to retrieve server list from NEWCOMPUTER: 64

It's seeing 2 servers now from OldComputer.

Let's do CDiag.

Take the following code (everything inside the "#####"). (Please verify computer
names and ip addresses).


   1. Open Notepad. Ensure that Format - Word Wrap is not checked. Highlight
then Copy the code (Ctrl-C), precisely as it is presented, and Paste (Ctrl-V)
into Notepad. Verify, and correct, names and addresses if necessary.
   2. Save the Notepad file as "cdiag.cmd", as type "All Files", into the root
folder "C:\".
   3. Run it by Start - Run - "c:\cdiag".
   4. Wait patiently.
   5. When Notepad opens up displaying c:\cdiag.txt, first check Format and
ensure that Word Wrap is NOT checked! Then, copy the entire contents (Ctrl-A
Ctrl-C) and paste (Ctrl-V) into your next post.


Do this from both computers, please, with both computers powered up and online.


##### Start CDiag Base Code

@echo off
set FullTarget1=OLDCOMPUTER 192.168.0.100
set FullTarget2=NEWCOMPUTER 192.168.0.101
set FullTarget3=
set FullTarget4=
set FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%
set FullTargets=%FullTargets% 127.0.0.1
set PingTargets=www.yahoo.com 66.94.230.32 192.168.0.1
Set Version=V1.32
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo AdHoc Browser View >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Full Targets %FullTargets% >>c:\cdiag.txt
for %%a in (%FullTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% net view %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view %%a >>c:\cdiag.txt
)
@echo. >>c:\cdiag.txt
@echo Ping Targets %PingTargets% >>c:\cdiag.txt
for %%a in (%PingTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
)
@echo. >>c:\cdiag.txt
@echo End diagnosis for %computername% >>c:\cdiag.txt
notepad c:\cdiag.txt
##### End CDiag Base Code

This seems like some serious problem I have here. Have gratefully and humbly
done as you say. Most recent output from browstat was taken just before I
posted, after uninstalling NIS from A (oldcomputer). Here is the CDiag output:

CDiagnosis V1.32
Start diagnosis for OLDCOMPUTER

AdHoc Browser View

Server Name            Remark
-------------------------------------------------------------------------------
\\NEWCOMPUTER                                                               

\\OLDCOMPUTER          Old Computer                                         

The command completed successfully.


Full Targets OLDCOMPUTER 192.168.0.100 NEWCOMPUTER 192.168.0.101   127.0.0.1

Target OLDCOMPUTER

"OLDCOMPUTER ping OLDCOMPUTER"



Pinging OLDCOMPUTER [192.168.0.100] with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.0.100:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms


"OLDCOMPUTER net view OLDCOMPUTER"

Shared resources at OLDCOMPUTER

Old Computer

Share name  Type   Used as  Comment             
-------------------------------------------------------------------------------
Printer     Print           Samsung SF-5100P    
Printer2    Print           Canon MP730 Printer 
SharedDocs  Disk                                
The command completed successfully.


Target 192.168.0.100

"OLDCOMPUTER ping 192.168.0.100"



Pinging 192.168.0.100 with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.0.100:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms


"OLDCOMPUTER net view 192.168.0.100"

Shared resources at 192.168.0.100

Old Computer

Share name  Type   Used as  Comment             
-------------------------------------------------------------------------------
Printer     Print           Samsung SF-5100P    
Printer2    Print           Canon MP730 Printer 
SharedDocs  Disk                                
The command completed successfully.


Target NEWCOMPUTER

"OLDCOMPUTER ping NEWCOMPUTER"



Pinging NEWCOMPUTER [192.168.0.101] with 32 bytes of data:



Reply from 192.168.0.101: bytes=32 time=3ms TTL=128

Reply from 192.168.0.101: bytes=32 time=4ms TTL=128

Reply from 192.168.0.101: bytes=32 time=4ms TTL=128

Reply from 192.168.0.101: bytes=32 time=3ms TTL=128



Ping statistics for 192.168.0.101:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 3ms, Maximum = 4ms, Average = 3ms


"OLDCOMPUTER net view NEWCOMPUTER"

Shared resources at NEWCOMPUTER



Share name  Type   Used as  Comment             
-------------------------------------------------------------------------------
Printer     Print           Canon MP730 Printer 
The command completed successfully.


Target 192.168.0.101

"OLDCOMPUTER ping 192.168.0.101"



Pinging 192.168.0.101 with 32 bytes of data:



Reply from 192.168.0.101: bytes=32 time=3ms TTL=128

Reply from 192.168.0.101: bytes=32 time=3ms TTL=128

Reply from 192.168.0.101: bytes=32 time=4ms TTL=128

Reply from 192.168.0.101: bytes=32 time=4ms TTL=128



Ping statistics for 192.168.0.101:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 3ms, Maximum = 4ms, Average = 3ms


"OLDCOMPUTER net view 192.168.0.101"

Shared resources at 192.168.0.101



Share name  Type   Used as  Comment             
-------------------------------------------------------------------------------
Printer     Print           Canon MP730 Printer 
The command completed successfully.


Target 127.0.0.1

"OLDCOMPUTER ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



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

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

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

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



Ping statistics for 127.0.0.1:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms


"OLDCOMPUTER net view 127.0.0.1"

Shared resources at 127.0.0.1

Old Computer

Share name  Type   Used as  Comment             
-------------------------------------------------------------------------------
Printer     Print           Samsung SF-5100P    
Printer2    Print           Canon MP730 Printer 
SharedDocs  Disk                                
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32 192.168.0.1

Target www.yahoo.com

"OLDCOMPUTER ping www.yahoo.com"



Pinging www.yahoo.akadns.net [66.94.230.45] with 32 bytes of data:



Reply from 66.94.230.45: bytes=32 time=180ms TTL=49

Reply from 66.94.230.45: bytes=32 time=182ms TTL=49

Reply from 66.94.230.45: bytes=32 time=178ms TTL=49

Reply from 66.94.230.45: bytes=32 time=182ms TTL=49



Ping statistics for 66.94.230.45:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 178ms, Maximum = 182ms, Average = 180ms


Target 66.94.230.32

"OLDCOMPUTER ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=183ms TTL=49

Reply from 66.94.230.32: bytes=32 time=179ms TTL=49

Reply from 66.94.230.32: bytes=32 time=181ms TTL=49

Reply from 66.94.230.32: bytes=32 time=179ms TTL=49



Ping statistics for 66.94.230.32:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 179ms, Maximum = 183ms, Average = 180ms


Target 192.168.0.1

"OLDCOMPUTER ping 192.168.0.1"



Pinging 192.168.0.1 with 32 bytes of data:



Reply from 192.168.0.1: bytes=32 time=2ms TTL=127

Reply from 192.168.0.1: bytes=32 time=2ms TTL=127

Reply from 192.168.0.1: bytes=32 time=2ms TTL=127

Reply from 192.168.0.1: bytes=32 time=2ms TTL=127



Ping statistics for 192.168.0.1:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 2ms, Maximum = 2ms, Average = 2ms


End diagnosis for OLDCOMPUTER

CDiagnosis V1.32
Start diagnosis for NEWCOMPUTER

AdHoc Browser View

Server Name            Remark
-------------------------------------------------------------------------------
\\NEWCOMPUTER                                                               

\\OLDCOMPUTER          Old Computer                                         

The command completed successfully.


Full Targets OLDCOMPUTER 192.168.0.100 NEWCOMPUTER 192.168.0.101   127.0.0.1

Target OLDCOMPUTER

"NEWCOMPUTER ping OLDCOMPUTER"



Pinging OLDCOMPUTER [192.168.0.100] with 32 bytes of data:



Reply from 192.168.0.100: bytes=32 time=3ms TTL=128

Reply from 192.168.0.100: bytes=32 time=4ms TTL=128

Reply from 192.168.0.100: bytes=32 time=4ms TTL=128

Reply from 192.168.0.100: bytes=32 time=4ms TTL=128



Ping statistics for 192.168.0.100:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 3ms, Maximum = 4ms, Average = 3ms


"NEWCOMPUTER net view OLDCOMPUTER"

Shared resources at OLDCOMPUTER

Old Computer

Share name  Type   Used as  Comment             
-------------------------------------------------------------------------------
Printer     Print           Samsung SF-5100P    
Printer2    Print           Canon MP730 Printer 
SharedDocs  Disk   (UNC)                        
The command completed successfully.


Target 192.168.0.100

"NEWCOMPUTER ping 192.168.0.100"



Pinging 192.168.0.100 with 32 bytes of data:



Reply from 192.168.0.100: bytes=32 time=4ms TTL=128

Reply from 192.168.0.100: bytes=32 time=3ms TTL=128

Reply from 192.168.0.100: bytes=32 time=4ms TTL=128

Reply from 192.168.0.100: bytes=32 time=6ms TTL=128



Ping statistics for 192.168.0.100:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 3ms, Maximum = 6ms, Average = 4ms


"NEWCOMPUTER net view 192.168.0.100"

Shared resources at 192.168.0.100

Old Computer

Share name  Type   Used as  Comment             
-------------------------------------------------------------------------------
Printer     Print           Samsung SF-5100P    
Printer2    Print           Canon MP730 Printer 
SharedDocs  Disk                                
The command completed successfully.


Target NEWCOMPUTER

"NEWCOMPUTER ping NEWCOMPUTER"



Pinging NEWCOMPUTER [192.168.0.101] with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.0.101:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms


"NEWCOMPUTER net view NEWCOMPUTER"

Shared resources at NEWCOMPUTER



Share name  Type   Used as  Comment             
-------------------------------------------------------------------------------
Printer     Print           Canon MP730 Printer 
The command completed successfully.


Target 192.168.0.101

"NEWCOMPUTER ping 192.168.0.101"



Pinging 192.168.0.101 with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.0.101:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms


"NEWCOMPUTER net view 192.168.0.101"

Shared resources at 192.168.0.101



Share name  Type   Used as  Comment             
-------------------------------------------------------------------------------
Printer     Print           Canon MP730 Printer 
The command completed successfully.


Target 127.0.0.1

"NEWCOMPUTER ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



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

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

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

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



Ping statistics for 127.0.0.1:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms


"NEWCOMPUTER net view 127.0.0.1"

Shared resources at 127.0.0.1



Share name  Type   Used as  Comment             
-------------------------------------------------------------------------------
Printer     Print           Canon MP730 Printer 
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32 192.168.0.1

Target www.yahoo.com

"NEWCOMPUTER ping www.yahoo.com"



Pinging www.yahoo.akadns.net [66.94.230.45] with 32 bytes of data:



Reply from 66.94.230.45: bytes=32 time=184ms TTL=49

Reply from 66.94.230.45: bytes=32 time=189ms TTL=49

Reply from 66.94.230.45: bytes=32 time=177ms TTL=49

Reply from 66.94.230.45: bytes=32 time=199ms TTL=49



Ping statistics for 66.94.230.45:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 177ms, Maximum = 199ms, Average = 187ms


Target 66.94.230.32

"NEWCOMPUTER ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=201ms TTL=49

Reply from 66.94.230.32: bytes=32 time=188ms TTL=49

Reply from 66.94.230.32: bytes=32 time=178ms TTL=49

Reply from 66.94.230.32: bytes=32 time=181ms TTL=49



Ping statistics for 66.94.230.32:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 178ms, Maximum = 201ms, Average = 187ms


Target 192.168.0.1

"NEWCOMPUTER ping 192.168.0.1"



Pinging 192.168.0.1 with 32 bytes of data:



Reply from 192.168.0.1: bytes=32 time=1ms TTL=127

Reply from 192.168.0.1: bytes=32 time=1ms TTL=127

Reply from 192.168.0.1: bytes=32 time=1ms TTL=127

Reply from 192.168.0.1: bytes=32 time=1ms TTL=127



Ping statistics for 192.168.0.1:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 1ms, Maximum = 1ms, Average = 1ms


End diagnosis for NEWCOMPUTER


Show quoteHide quote

On Sat, 11 Jun 2005 23:40:01 -0700, slowey <slo***@discussions.microsoft.com>
wrote:

So what problem exactly are you still seeing?  I don't see any problems with
either computer pinging the other, nor with either computer seeing each other in
general?  Are we maybe looking at a share problem?

What edition (Home or Pro) and file sharing (simple or advanced) is each
computer running?
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html>

Thanks Chuck. I think the problem is now solved. I ran the Network
configuration wizard on both computers and file and printer sharing worked
fine. It's great when things work as they are supposed to! Then I installed
NIS on both computers and by using the networking wizard file sharing still
worked!

Thanks very much for all your help Chuck. To sum up it seems that the root
of my problems was that when I got my second computer a while back I should
have uninstalled NIS and set up wireless networking properly before
reinstalling NIS. Not sure that we discovered any other problems in all that
diagnostics.

Again, thanks!
Show quoteHide quote

Ready to use portable hd instead of networking headache!
Problems adding Media Center computer to home network with 98s.
No connection to router web access page
VPN DNS quit working
Question about sharing on network with two users same machine....HELP
Help! Problem with network
Cannot ping myself
Can a networked CD drive look like a CD drive from another computer?
Cannot connect to IE
ICS and Networking