2 different networks at the same time?

G

Guest

I have a laptop that runs XP Professional that is a member of a domain at
work. I would like to set up a home network in which I would like to connect
a computer that's running XP Media Edition 2005. How can I do this?
 
R

Robert L [MS-MVP]

You can keep the domain setup while logon local computer at home. You also need to setup the same username and password in all computers at home for sharing.

workgroup networking faqs How can I share files between workgroup computer and domain/workgroup computer There are currently no logon servers available to service the logon request ...
www.chicagotech.net/workgroupnet.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
I have a laptop that runs XP Professional that is a member of a domain at
work. I would like to set up a home network in which I would like to connect
a computer that's running XP Media Edition 2005. How can I do this?
 
C

Chuck

I have a laptop that runs XP Professional that is a member of a domain at
work. I would like to set up a home network in which I would like to connect
a computer that's running XP Media Edition 2005. How can I do this?

Ken,

Run the Network Setup Wizard on your home computer. That will give it the
network components and services. Then you change the workgroup membership of
the laptop, making it the same as the name of the domain at work. That will
allow visibility in My Network Places.
<http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html>
http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html

Finally, setup and activate a common, non-Guest account with identical non-blank
password on each computer.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Activate>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Activate
 
G

Guest

Are you saying that, even though I'm a member of a domain at work currently,
I can also join a workgroup for the home network, too?
 
C

Chuck

Are you saying that, even though I'm a member of a domain at work currently,
I can also join a workgroup for the home network, too?

No, Ken,

Any computer can join only ONE domain or workgroup at any time. To make it
easiest to see the home computer and laptop from each other, you make the home
computer a member of a workgroup that has the same name as the laptop. Please
do NOT change the domain membership on the laptop.

You need to do this for the browser. I'm betting that the laptop won't be
running the browser, so the home computer needs to be in a workgroup with the
same name as the domain. Details are in the article:
<http://nitecruzr.blogspot.com/2005/07/windows-networking.html>
http://nitecruzr.blogspot.com/2005/07/windows-networking.html
 
G

Guest

I've created a workgroup name on the
home computer with the same name as the domain of
the work computer. I've created an administrator account
on the home computer with the same name and password
as the account on the work computer. However, I
simply renamed an existing account on the home computer to
match the account on the work computer. I have the
following observations:

Home computer:
• when I left click on my network places, I can see
the shared folders on the work computer, but none
are accessible
• when I click on workgroups from the home computer,
the work computer is not visible (however, I don't
know if it should be)

Work computer:
• The shared folder on the home computer is
accessible, but I never did anything to allow it
beyond running the Network Setup Wizard. Is the
folder simply available to anybody?
• What I left click on my network places-entire
network-Microsoft windows network-(workgroup)-(home
computer) appears

In summary, 1) I can access the shared folder on the
home computer from my work computer just fine, but
I'm concerned that anybody has access to that folder. I
don't think it's any big deal for the home network,
but I am concerned about potential problems from the
internet. I really don't know anything about
workgroup security. Also, 2) shared folders of the work
computer are visible on the home computer, but are
inaccessible.
 
C

Chuck

I've created a workgroup name on the
home computer with the same name as the domain of
the work computer. I've created an administrator account
on the home computer with the same name and password
as the account on the work computer. However, I
simply renamed an existing account on the home computer to
match the account on the work computer. I have the
following observations:

Home computer:
• when I left click on my network places, I can see
the shared folders on the work computer, but none
are accessible
• when I click on workgroups from the home computer,
the work computer is not visible (however, I don't
know if it should be)

Work computer:
• The shared folder on the home computer is
accessible, but I never did anything to allow it
beyond running the Network Setup Wizard. Is the
folder simply available to anybody?
• What I left click on my network places-entire
network-Microsoft windows network-(workgroup)-(home
computer) appears

In summary, 1) I can access the shared folder on the
home computer from my work computer just fine, but
I'm concerned that anybody has access to that folder. I
don't think it's any big deal for the home network,
but I am concerned about potential problems from the
internet. I really don't know anything about
workgroup security. Also, 2) shared folders of the work
computer are visible on the home computer, but are
inaccessible.

Ken,

We need to discuss this in two separate tasks - visibility and accessibility.

Visibility involves getting the browser system to work (I'm not discussing
Internet Explorer here). If the workgroup (on the home system) is identical to
the domain membership (on the laptop), then you make sure that one and only one
computer is running the browser. Read about the browser please:
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html

Let's look at "browstat status", "ipconfig /all", "net config server", and "net
config workstation", from each computer, with both computers online together, so
we can 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

Once we get visibility working, we'll tackle accessibility.
 
G

Guest

Before I tried to diagnose the problem with "browstat status", I looked at
the situation on both computers one more time. I understand your statement
about separating the problem into visibility and accessibility. Focusing on
visibility, I took a look at My Network Places on both computers one more
time. As I looked at each computer again, I concluded that I could see the
shared folders on each computer. However, they looked different from each
other.

When I left clicked on My Network Places on the work computer, the items I
saw included "Entire Network", the server at work, and the shared documents
folder on the home computer (Chuck, because I can't attach anything to this
message, I'm e-mailing these screenshots directly to you). When I click on
"Entire Network", eventually the home computer appears in the shared
documents appear. While it didn't do this last time, when I clicked on the
shared documents folder either after "Entire Network" or directly after left
clicking on My Network Places, this time a window popped up and asked me for
my username and password. Just for the heck of it, I put in an account on the
home computer that didn't match an account on the work computer. It accepted
that account, and I could view the files in the shared folders on the home
computer from the work computer.

When I left clicked on My Network Places from the home computer, the shared
folders from my work computer appeared. I wasn't able to access any files on
my work computer from my home computer. This is unchanged from before.

Thus, I believe both computers are visible to each other, but in different
ways.
 
C

Chuck

Before I tried to diagnose the problem with "browstat status", I looked at
the situation on both computers one more time. I understand your statement
about separating the problem into visibility and accessibility. Focusing on
visibility, I took a look at My Network Places on both computers one more
time. As I looked at each computer again, I concluded that I could see the
shared folders on each computer. However, they looked different from each
other.

When I left clicked on My Network Places on the work computer, the items I
saw included "Entire Network", the server at work, and the shared documents
folder on the home computer (Chuck, because I can't attach anything to this
message, I'm e-mailing these screenshots directly to you). When I click on
"Entire Network", eventually the home computer appears in the shared
documents appear. While it didn't do this last time, when I clicked on the
shared documents folder either after "Entire Network" or directly after left
clicking on My Network Places, this time a window popped up and asked me for
my username and password. Just for the heck of it, I put in an account on the
home computer that didn't match an account on the work computer. It accepted
that account, and I could view the files in the shared folders on the home
computer from the work computer.

When I left clicked on My Network Places from the home computer, the shared
folders from my work computer appeared. I wasn't able to access any files on
my work computer from my home computer. This is unchanged from before.

Thus, I believe both computers are visible to each other, but in different
ways.

Good job, Ken. I'll check my email and see what I can get out of your pictures.
Be patient here.

And since this thread may start getting long, I'll advise you to post your
answers after mine. Make it easier on both of us.
<http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting>
http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting
 
G

Guest

Chuck, two things:

1-I'm thinking the ball is in your court. Is that correct, or is there
something I should be doing?
2-I really don't know what you mean by "I'll advise you to post your
answers after mine." I'm not sure what I should do. In replying to your last
message I did delete all the prior messages.
 
C

Chuck

Chuck, two things:

1-I'm thinking the ball is in your court. Is that correct, or is there
something I should be doing?
2-I really don't know what you mean by "I'll advise you to post your
answers after mine." I'm not sure what I should do. In replying to your last
message I did delete all the prior messages.

OK, Ken,

That was the email issue the other night. Couldn't remember, when I got it
open. OK, I'm looking at 3 pictures, but not really sure what they depict. And
bitmaps of screen objects aren't really readable either - my eyes aren't quite
that good.

Let's try again.
# Net view >c:\netview.txt
# Notepad c:\netview.txt
Run those two from a command window. Copy and paste text into your next post.
And add a description, for each computer, what operating system on the computer.

And since you ask, this is me posting after your answers. Don't worry about
deleting, I'll do that periodically. Retaining context makes it easier for me
to find previous discussions.
<http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting>
http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting
 
G

Guest

I guess I still don't know what I need to do you to post after your answers.
I'm using Microsoft's reader and I just click on "reply". Should I be doing
something differently?

As you requested, following your instructions, this is the result on the
work computer running XP Professional:

Server Name Remark

-------------------------------------------------------------------------------
\\JANET

\\WOLFEKE Ken Wolfe

The command completed successfully.

Below is the home computer, running XP Media Edition:
Server Name Remark

-------------------------------------------------------------------------------
\\JANET

\\WOLFEKE Ken Wolfe

The command completed successfully.
 
G

Guest

Ken W said:
I guess I still don't know what I need to do you to post after your answers.
I'm using Microsoft's reader and I just click on "reply". Should I be doing
something differently?

As you requested, following your instructions, this is the result on the
work computer running XP Professional:

Server Name Remark

-------------------------------------------------------------------------------
\\JANET

\\WOLFEKE Ken Wolfe

The command completed successfully.

Below is the home computer, running XP Media Edition:
Server Name Remark

-------------------------------------------------------------------------------
\\JANET

\\WOLFEKE Ken Wolfe

The command completed successfully.

Hi Ken,

This is me replying after your post, using the Microsoft reader (aka the CDO).

When you hit Reply, the cursor is positioned above the provious thread.
Hold down Ctrl, and hit End. That will place the cursor after the previous
thread.

Now we'll see what this looks like.
 
C

Chuck

I guess I still don't know what I need to do you to post after your answers.
I'm using Microsoft's reader and I just click on "reply". Should I be doing
something differently?

As you requested, following your instructions, this is the result on the
work computer running XP Professional:

Server Name Remark

-------------------------------------------------------------------------------
\\JANET

\\WOLFEKE Ken Wolfe

The command completed successfully.

Below is the home computer, running XP Media Edition:
Server Name Remark

-------------------------------------------------------------------------------
\\JANET

\\WOLFEKE Ken Wolfe

The command completed successfully.

OK, Ken,

I covered (hopefully tested) the bottom posting issue in my other post. So
let's address the problem.

So both computers see each other, in "net view".

Now "net view" gives a high level view of the network, from each computer. To
diagnose this problem, we need "browstat status", "ipconfig /all", "net config
server", and "net config workstation", from each computer.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp
 
G

Guest

Chuck said:
OK, Ken,

I covered (hopefully tested) the bottom posting issue in my other post. So
let's address the problem.

So both computers see each other, in "net view".

Now "net view" gives a high level view of the network, from each computer. To
diagnose this problem, we need "browstat status", "ipconfig /all", "net config
server", and "net config workstation", from each computer.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp
Thanks for the instructions on how to post under a message. I think I did it
this time. Hopefully, it worked.

Here are the results for the work computer, running windows XP Professional
SP2:
Status for domain HORIZONTECH on transport
\Device\NetBT_Tcpip_{6D119389-0FE1-460B-A324-E3FA6635DF9B}
Browsing is active on domain.
Master browser name is: WOLFEKE
Master browser is running build 2600
1 backup servers retrieved from master WOLFEKE
\\WOLFEKE
There are 2 servers in domain HORIZONTECH on transport
\Device\NetBT_Tcpip_{6D119389-0FE1-460B-A324-E3FA6635DF9B}
There are 1 domains in domain HORIZONTECH on transport
\Device\NetBT_Tcpip_{6D119389-0FE1-460B-A324-E3FA6635DF9B}

Windows IP Configuration



Host Name . . . . . . . . . . . . : WOLFEKE

Primary Dns Suffix . . . . . . . : horizontechnology.local

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : horizontechnology.local



Ethernet adapter Wireless Network Connection:



Media State . . . . . . . . . . . : Media disconnected

Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG
Network Connection

Physical Address. . . . . . . . . : 00-0E-35-6F-9C-86



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Broadcom 570x Gigabit Integrated
Controller

Physical Address. . . . . . . . . : 00-0F-1F-C4-AC-20

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.102

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 166.102.165.11

166.102.165.13

Lease Obtained. . . . . . . . . . : Wednesday, June 14, 2006 5:28:03
PM

Lease Expires . . . . . . . . . . : Thursday, June 15, 2006 5:28:03 PM

Server Name \\WOLFEKE
Server Comment Ken Wolfe

Software version Windows 2002
Server is active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{6D119389-0FE1-460B-A324-E3FA6635DF9B} (000f1fc4ac20)


Server hidden No
Maximum Logged On Users 10
Maximum open files per session 16384

Idle session time (min) 15
The command completed successfully.

Now for the home computer, running Microsoft Media Edition:
Status for domain HORIZONTECH on transport
\Device\NetBT_Tcpip_{A9FAAC9A-A90F-4F0A-8387-F5DDA6F0FA76}
Browsing is active on domain.
Master browser name is: WOLFEKE
Master browser is running build 2600
1 backup servers retrieved from master WOLFEKE
\\WOLFEKE
There are 2 servers in domain HORIZONTECH on transport
\Device\NetBT_Tcpip_{A9FAAC9A-A90F-4F0A-8387-F5DDA6F0FA76}
There are 1 domains in domain HORIZONTECH on transport
\Device\NetBT_Tcpip_{A9FAAC9A-A90F-4F0A-8387-F5DDA6F0FA76}

Windows IP Configuration



Host Name . . . . . . . . . . . . : JANET

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection:



Media State . . . . . . . . . . . : Media disconnected

Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Controller

Physical Address. . . . . . . . . : 00-14-22-F5-0B-8F



Ethernet adapter Wireless Network Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG
Network Connection

Physical Address. . . . . . . . . : 00-13-02-5B-5B-C3

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.106

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 166.102.165.11

166.102.165.13

Lease Obtained. . . . . . . . . . : Thursday, June 15, 2006 8:01:10 AM

Lease Expires . . . . . . . . . . : Friday, June 16, 2006 8:01:10 AM

Server Name \\JANET
Server Comment

Software version Windows 2002
Server is active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{A9FAAC9A-A90F-4F0A-8387-F5DDA6F0FA76} (0013025b5bc3)


Server hidden No
Maximum Logged On Users 10
Maximum open files per session 16384

Idle session time (min) 15
The command completed successfully.

Computer name \\JANET
Full Computer name JANET
User name Mom & Dad

Workstation active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{A9FAAC9A-A90F-4F0A-8387-F5DDA6F0FA76} (0013025B5BC3)

Software version Windows 2002

Workstation domain HORIZONTECH
Workstation Domain DNS Name (null)
Logon domain JANET

COM Open Timeout (sec) 0
COM Send Count (byte) 16
COM Send Timeout (msec) 250
The command completed successfully.
 
C

Chuck

Thanks for the instructions on how to post under a message. I think I did it
this time. Hopefully, it worked.

Here are the results for the work computer, running windows XP Professional
SP2:

<SNIP>

Ken,

You nailed it. The posting anyway.

The diagnostics, so far, are clean.
# Both computers on same physical segment 192.168.1.0/24.
# Both computers in same workgroup "HORIZONTECH", acknowledging the same master
browser "WOLFEKE", and seeing 2 computers.
# Both computers showing NetBT, neither hidden.

Let's do relational analysis. Take the following code (everything INSIDE the
"#####" lines). Please DO NOT include ANY portion of the "#####" lines. (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 all computers, please, with all computers powered up and online.

##### Start CDiag Assembled Code

@echo off
set FullTarget1=WOLFEKE 192.168.1.102
set FullTarget2=JANET 192.168.1.106
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.1.1
Set Version=V1.40
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo Full Targets %FullTargets% >>c:\cdiag.txt
@echo Ping Targets %PingTargets% >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Over All Analysis >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Enumerate Shares >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net share >>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 Analysis %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 Analysis %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
:EOF

##### End CDiag Assembled Code
 
G

Guest

Chuck said:
<SNIP>

Ken,

You nailed it. The posting anyway.

The diagnostics, so far, are clean.
# Both computers on same physical segment 192.168.1.0/24.
# Both computers in same workgroup "HORIZONTECH", acknowledging the same master
browser "WOLFEKE", and seeing 2 computers.
# Both computers showing NetBT, neither hidden.

Let's do relational analysis. Take the following code (everything INSIDE the
"#####" lines). Please DO NOT include ANY portion of the "#####" lines. (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 all computers, please, with all computers powered up and online.

##### Start CDiag Assembled Code

@echo off
set FullTarget1=WOLFEKE 192.168.1.102
set FullTarget2=JANET 192.168.1.106
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.1.1
Set Version=V1.40
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo Full Targets %FullTargets% >>c:\cdiag.txt
@echo Ping Targets %PingTargets% >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Over All Analysis >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Enumerate Shares >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net share >>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 Analysis %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 Analysis %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
:EOF

##### End CDiag Assembled Code

THE RESULTS FROM THE WORK COMPUTER:
CDiagnosis V1.40
Start diagnosis for WOLFEKE
Full Targets WOLFEKE 192.168.1.102 JANET 192.168.1.106 127.0.0.1
Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

Over All Analysis

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
ADMIN$ C:\WINDOWS Remote Admin

IPC$ Remote IPC

C$ C:\ Default share

ArgoData C:\_Data\My Documents\Horizon\Argos\ArgoData

Fax Cover Sheets
C:\_Data\My Documents\Horizon\Fax Cover Sheets

Quicken C:\_Data\My Documents\Quicken
Quotes-Ken PC
C:\_Data\My Documents\Horizon\Quotes

Share C:\Share
Statements C:\_Data\My Documents\Horizon\Financial\Financial
Statements\Statements

The command completed successfully.


Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\JANET

\\WOLFEKE Ken Wolfe

The command completed successfully.


Full Targets Analysis WOLFEKE 192.168.1.102 JANET 192.168.1.106 127.0.0.1

Target WOLFEKE

"WOLFEKE ping WOLFEKE"



Pinging WOLFEKE.horizontechnology.local [192.168.1.102] with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.1.102:

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

Approximate round trip times in milli-seconds:

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


"WOLFEKE net view WOLFEKE"

Shared resources at WOLFEKE

Ken Wolfe

Share name Type Used as Comment

-------------------------------------------------------------------------------
ArgoData Disk
Fax Cover Sheets Disk
Quicken Disk
Quotes-Ken PC Disk
Share Disk
Statements Disk
The command completed successfully.


Target 192.168.1.102

"WOLFEKE ping 192.168.1.102"



Pinging 192.168.1.102 with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.1.102:

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

Approximate round trip times in milli-seconds:

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


"WOLFEKE net view 192.168.1.102"


Target JANET

"WOLFEKE ping JANET"



Pinging JANET [192.168.1.106] with 32 bytes of data:



Reply from 192.168.1.106: bytes=32 time=44ms TTL=128

Reply from 192.168.1.106: bytes=32 time=65ms TTL=128

Reply from 192.168.1.106: bytes=32 time=88ms TTL=128

Reply from 192.168.1.106: bytes=32 time=8ms TTL=128



Ping statistics for 192.168.1.106:

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

Approximate round trip times in milli-seconds:

Minimum = 8ms, Maximum = 88ms, Average = 51ms


"WOLFEKE net view JANET"


Target 192.168.1.106

"WOLFEKE ping 192.168.1.106"



Pinging 192.168.1.106 with 32 bytes of data:



Reply from 192.168.1.106: bytes=32 time=60ms TTL=128

Reply from 192.168.1.106: bytes=32 time=84ms TTL=128

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

Reply from 192.168.1.106: bytes=32 time=26ms TTL=128



Ping statistics for 192.168.1.106:

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

Approximate round trip times in milli-seconds:

Minimum = 4ms, Maximum = 84ms, Average = 43ms


"WOLFEKE net view 192.168.1.106"


Target 127.0.0.1

"WOLFEKE 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


"WOLFEKE net view 127.0.0.1"


Ping Targets Analysis www.yahoo.com 66.94.230.32 192.168.1.1

Target www.yahoo.com

"WOLFEKE ping www.yahoo.com"



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



Reply from 68.142.197.85: bytes=32 time=84ms TTL=53

Reply from 68.142.197.85: bytes=32 time=83ms TTL=53

Reply from 68.142.197.85: bytes=32 time=84ms TTL=53

Reply from 68.142.197.85: bytes=32 time=83ms TTL=53



Ping statistics for 68.142.197.85:

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

Approximate round trip times in milli-seconds:

Minimum = 83ms, Maximum = 84ms, Average = 83ms


Target 66.94.230.32

"WOLFEKE ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=112ms TTL=52

Reply from 66.94.230.32: bytes=32 time=108ms TTL=52

Reply from 66.94.230.32: bytes=32 time=107ms TTL=52

Reply from 66.94.230.32: bytes=32 time=110ms TTL=52



Ping statistics for 66.94.230.32:

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

Approximate round trip times in milli-seconds:

Minimum = 107ms, Maximum = 112ms, Average = 109ms


Target 192.168.1.1

"WOLFEKE ping 192.168.1.1"



Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Ping statistics for 192.168.1.1:

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

Approximate round trip times in milli-seconds:

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


End diagnosis for WOLFEKE
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
THE RESULTS FROM THE HOME COMPUTER:
CDiagnosis V1.40
Start diagnosis for JANET
Full Targets WOLFEKE 192.168.1.102 JANET 192.168.1.106 127.0.0.1
Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

Over All Analysis

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers

C$ C:\ Default share

ADMIN$ C:\WINDOWS Remote Admin

IPC$ Remote IPC

SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS

Printer Microsoft Document Ima Spooled Microsoft Office Document Image
Wr
The command completed successfully.


Adhoc Browser View

Server Name Remark

-------------------------------------------------------------------------------
\\JANET

\\WOLFEKE Ken Wolfe

The command completed successfully.


Full Targets Analysis WOLFEKE 192.168.1.102 JANET 192.168.1.106 127.0.0.1

Target WOLFEKE

"JANET ping WOLFEKE"



Pinging WOLFEKE [192.168.1.102] with 32 bytes of data:



Reply from 192.168.1.102: bytes=32 time=1ms TTL=128

Reply from 192.168.1.102: bytes=32 time=2ms TTL=128

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

Reply from 192.168.1.102: bytes=32 time=2ms TTL=128



Ping statistics for 192.168.1.102:

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

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 3ms, Average = 2ms


"JANET net view WOLFEKE"

Shared resources at WOLFEKE

Ken Wolfe

Share name Type Used as Comment

-------------------------------------------------------------------------------
ArgoData Disk
Fax Cover Sheets Disk
Quicken Disk
Quotes-Ken PC Disk
Share Disk
Statements Disk
The command completed successfully.


Target 192.168.1.102

"JANET ping 192.168.1.102"



Pinging 192.168.1.102 with 32 bytes of data:



Reply from 192.168.1.102: bytes=32 time=1ms TTL=128

Reply from 192.168.1.102: bytes=32 time=2ms TTL=128

Reply from 192.168.1.102: bytes=32 time=2ms TTL=128

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



Ping statistics for 192.168.1.102:

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

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 3ms, Average = 2ms


"JANET net view 192.168.1.102"

Shared resources at 192.168.1.102

Ken Wolfe

Share name Type Used as Comment

-------------------------------------------------------------------------------
ArgoData Disk
Fax Cover Sheets Disk
Quicken Disk
Quotes-Ken PC Disk
Share Disk
Statements Disk
The command completed successfully.


Target JANET

"JANET ping JANET"



Pinging JANET [192.168.1.106] with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.1.106:

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

Approximate round trip times in milli-seconds:

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


"JANET net view JANET"

Shared resources at JANET



Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.


Target 192.168.1.106

"JANET ping 192.168.1.106"



Pinging 192.168.1.106 with 32 bytes of data:



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

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

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

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



Ping statistics for 192.168.1.106:

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

Approximate round trip times in milli-seconds:

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


"JANET net view 192.168.1.106"

Shared resources at 192.168.1.106



Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.


Target 127.0.0.1

"JANET 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


"JANET net view 127.0.0.1"

Shared resources at 127.0.0.1



Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.


Ping Targets Analysis www.yahoo.com 66.94.230.32 192.168.1.1

Target www.yahoo.com

"JANET ping www.yahoo.com"



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



Reply from 68.142.197.68: bytes=32 time=96ms TTL=53

Reply from 68.142.197.68: bytes=32 time=87ms TTL=53

Reply from 68.142.197.68: bytes=32 time=140ms TTL=53

Reply from 68.142.197.68: bytes=32 time=149ms TTL=53



Ping statistics for 68.142.197.68:

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

Approximate round trip times in milli-seconds:

Minimum = 87ms, Maximum = 149ms, Average = 118ms


Target 66.94.230.32

"JANET ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=197ms TTL=52

Reply from 66.94.230.32: bytes=32 time=131ms TTL=52

Reply from 66.94.230.32: bytes=32 time=155ms TTL=52

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



Ping statistics for 66.94.230.32:

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

Approximate round trip times in milli-seconds:

Minimum = 131ms, Maximum = 197ms, Average = 165ms


Target 192.168.1.1

"JANET ping 192.168.1.1"



Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time=4ms TTL=64

Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Reply from 192.168.1.1: bytes=32 time=2ms TTL=64



Ping statistics for 192.168.1.1:

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

Approximate round trip times in milli-seconds:

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


End diagnosis for JANET
 
C

Chuck


<BIG SNIP>

OK, Ken,

CDiag shows 2 positives:
# WOLFEKE cannot "net view" itself by IP address - neither as "192.168.1.102",
nor as "127.0.0.1".
# JANET, on the other hand, CAN "net view" WOLFEKE, as "192.168.1.102".

First, is NetBT explicitly Enabled on WOLFEKE?
<http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html>
http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html

Next, are there any misconfigured or overlooked personal firewalls, or other
security component on WOLFEKE? 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

Finally, we'll look at LSP / Winsock / TCP/IP corruption.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
 
G

Guest

Chuck said:
<BIG SNIP>

OK, Ken,

CDiag shows 2 positives:
# WOLFEKE cannot "net view" itself by IP address - neither as "192.168.1.102",
nor as "127.0.0.1".
# JANET, on the other hand, CAN "net view" WOLFEKE, as "192.168.1.102".

First, is NetBT explicitly Enabled on WOLFEKE?
<http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html>
http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html

Next, are there any misconfigured or overlooked personal firewalls, or other
security component on WOLFEKE? 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

Finally, we'll look at LSP / Winsock / TCP/IP corruption.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
I explicitly enabled NetBT per your instructions on both computers. They
were both set to default. I then tried to read shared folders of the work
computer (WOLFEKE) from the home computer (JANET) (you may recall that it
seems to work fine the other way - work (WOLFEKE) is able to read and write
files on home (JANET)). All of the shared folders that I created on WOLFEKE
were not accessible, but the WOLFEKE\SHARE folder that XP created was both
read and write accessible. It's possible that it's always been this way
because I never checked every shared folder before, but there is definitely,
at least now, a difference between shared folders that I created and the
shared folder that XP created on the work computer (WOLFEKE).

I didn't try your other suggestions below making sure NetBT was enabled on
both machines because I didn't think it was relevant anymore in light of the
information I learned in the previous paragraph.
 
C

Chuck

I explicitly enabled NetBT per your instructions on both computers. They
were both set to default. I then tried to read shared folders of the work
computer (WOLFEKE) from the home computer (JANET) (you may recall that it
seems to work fine the other way - work (WOLFEKE) is able to read and write
files on home (JANET)). All of the shared folders that I created on WOLFEKE
were not accessible, but the WOLFEKE\SHARE folder that XP created was both
read and write accessible. It's possible that it's always been this way
because I never checked every shared folder before, but there is definitely,
at least now, a difference between shared folders that I created and the
shared folder that XP created on the work computer (WOLFEKE).

I didn't try your other suggestions below making sure NetBT was enabled on
both machines because I didn't think it was relevant anymore in light of the
information I learned in the previous paragraph.

Ken,

OK, with NetBT properly Enabled, we have a start. Now, if you have a situation
where some folders are accessible, and others aren't, you have to adjust
permissioning.
<http://nitecruzr.blogspot.com/2005/11/irregularities-in-individual-share.html>
http://nitecruzr.blogspot.com/2005/11/irregularities-in-individual-share.html

So let's try one suggestion at a time. LSP / Winsock corruption may not be an
issue here. That's good news. Keep going now.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top