>Hello Group:
>I have been trying to troubleshoot a problem with networking two
>Windows XP Pro/SP2 computers, connected through a linksys router. The
>problem:  Shared files on computer A  are not seen by computer B,
>whereas computer A can see shared files on computer B.
>The problem isn't solved yet, but in troubleshooting, I came up with
>this additional problem:
>When I run netdiag /test:winsock on computer A, I get these lines in
>the output:
>Computer name: AMD64
>DNS host name: AMD64
>System Info: Windows 2000 Professional (Build 2600)
>etc
>etc
>
>But, Windows XP Pro /SP2 is the only operating system which has ever
>been installed on this computer.
>
>What can be going on here?
>I will post details of my primary sharing problem later, but I'm
>curious about what may be causing this tool to "think" I have Win2K
>installed? And could that be part of my problem?
>
>Many thanks.
>
>Jack

>Hello Group:
>I have been trying to troubleshoot a problem with networking two
>Windows XP Pro/SP2 computers, connected through a linksys router. The
>problem:  Shared files on computer A  are not seen by computer B,
>whereas computer A can see shared files on computer B.
>The problem isn't solved yet, but in troubleshooting, I came up with
>this additional problem:
>When I run netdiag /test:winsock on computer A, I get these lines in
>the output:
>Computer name: AMD64
>DNS host name: AMD64
>System Info: Windows 2000 Professional (Build 2600)
>etc
>etc
>
>But, Windows XP Pro /SP2 is the only operating system which has ever
>been installed on this computer.
>
>What can be going on here?
>I will post details of my primary sharing problem later, but I'm
>curious about what may be causing this tool to "think" I have Win2K
>installed? And could that be part of my problem?
>
>Many thanks.
>
>Jack

>On Sat, 29 Jul 2006 22:17:42 GMT, JClark <jcl***@invalid.invalid.com> wrote:
>
>>Hello Group:
>>I have been trying to troubleshoot a problem with networking two
>>Windows XP Pro/SP2 computers, connected through a linksys router. The
>>problem:  Shared files on computer A  are not seen by computer B,
>>whereas computer A can see shared files on computer B.
>>The problem isn't solved yet, but in troubleshooting, I came up with
>>this additional problem:
>>When I run netdiag /test:winsock on computer A, I get these lines in
>>the output:
>>Computer name: AMD64
>>DNS host name: AMD64
>>System Info: Windows 2000 Professional (Build 2600)
>>etc
>>etc
>>
>>But, Windows XP Pro /SP2 is the only operating system which has ever
>>been installed on this computer.
>>
>>What can be going on here?
>>I will post details of my primary sharing problem later, but I'm
>>curious about what may be causing this tool to "think" I have Win2K
>>installed? And could that be part of my problem?
>>
>>Many thanks.
>>
>>Jack
>
>Jack,
>
>Windows 2000 is Windows NT V5.0.  Windows XP is Windows NT V5.1.  I just ran
>Netdiag on my computer with XP Pro, and it too gave me "Windows 2000
>Professional (Build 2600)".
>
>One of the most common causes of this problem would be a misconfigured or
>overlooked personal firewall, or other security component. There are several
>other possibilities too, and any might be the cause of your problem. Read this
>article with an open mind.
><http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
>http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html
>
>Try "browstat status", "ipconfig /all", "net config server", and "net config
>workstation", from each computer, to better diagnose the problem.  Read this
>article, and linked articles, and follow instructions precisely (download
>browstat!):
><http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
>http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp
Chuck

>On Sat, 29 Jul 2006 15:53:31 -0700, Chuck <n***@example.net> wrote:
>
>>On Sat, 29 Jul 2006 22:17:42 GMT, JClark <jcl***@invalid.invalid.com> wrote:
>>
>>>Hello Group:
>>>I have been trying to troubleshoot a problem with networking two
>>>Windows XP Pro/SP2 computers, connected through a linksys router. The
>>>problem:  Shared files on computer A  are not seen by computer B,
>>>whereas computer A can see shared files on computer B.
>>>The problem isn't solved yet, but in troubleshooting, I came up with
>>>this additional problem:
>>>When I run netdiag /test:winsock on computer A, I get these lines in
>>>the output:
>>>Computer name: AMD64
>>>DNS host name: AMD64
>>>System Info: Windows 2000 Professional (Build 2600)
>>>etc
>>>etc
>>>
>>>But, Windows XP Pro /SP2 is the only operating system which has ever
>>>been installed on this computer.
>>>
>>>What can be going on here?
>>>I will post details of my primary sharing problem later, but I'm
>>>curious about what may be causing this tool to "think" I have Win2K
>>>installed? And could that be part of my problem?
>>>
>>>Many thanks.
>>>
>>>Jack
>>
>>Jack,
>>
>>Windows 2000 is Windows NT V5.0.  Windows XP is Windows NT V5.1.  I just ran
>>Netdiag on my computer with XP Pro, and it too gave me "Windows 2000
>>Professional (Build 2600)".
>>
>>One of the most common causes of this problem would be a misconfigured or
>>overlooked personal firewall, or other security component. There are several
>>other possibilities too, and any might be the cause of your problem. Read this
>>article with an open mind.
>><http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
>>http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html
>>
>>Try "browstat status", "ipconfig /all", "net config server", and "net config
>>workstation", from each computer, to better diagnose the problem.  Read this
>>article, and linked articles, and follow instructions precisely (download
>>browstat!):
>><http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
>>http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp
>Chuck
>Yes, I also tried netdiag on another XP machine and got the same
>thing. I guess netdiag is, like so many other MS tools, an older win2k
>design.
>
>With regard to my "one way street" networking problem, I've been
>working on it for a week and have gone through many things, including
>the firewalls (rules are allowing it). I've changed the router and
>TCP/IP configurations until I'm seeing them in my dreams. I was
>wondering if I might have a corrupted TCP/IP and was following MS
>recommendations, when I saw the "error" in identification of my OS and
>thought I'd better stop there. Now that that has been explained, I
>will certainly follow your advice regarding the website and the
>suggestions. I'll report results to the group as followup to this
>thread. It may take a few days.
>Again, I appreciate very much your thoughts and advice.
>
>Jack