W2K Domain-Connected Laptop -> XP Workgroup Desktop via Crossover

G

Guest

Hello - I think from reading prior posts I'm going to be asking a similar
question to one that has been asked many times. Apologies if this is going to
sound repetitive.

I'm trying to permit the exchange of data between my office PC (a W2K laptop
that is a member of a corporate domain) and my home PC (a standalone XP Home
Edition PC configured as a workgroup member).

Connection is via a crossover cable. No routers to content with.

Here's what I know about the office laptop:
- DHCP enabled
- I have admin rights either via a cached account on the domain or through
an account local to the PC (both are available)
- I'm quite certain there are some policy restrictions that the laptop is
adhering to (by virtue of its membership in the corporate domain) but
wouldn't know where to research what they consist of. Hopefully this is not
an issue.

Things I've tried:

1. The obvious first thing I did was to enabled File and Print sharing on
the home PC, and to actually set-up a share on both boxes (open to everyone,
no restrictions).

2. Disabled the XP firewall completely.

3. Programmed a static IP of a.b.c.1 and a gateway of a.b.c.1 on the home
PC; programmed a static IP of a.b.c.2 and a gateway of a.b.c.1 on the office
PC (... this is suboptimal - I would really rather avoid having to do this,
since it involves switching things back and forth every time I want to bring
the laptop home)

Result ->
: Office PC and Home PC both recognize each other when the cable is
connected ("Local Area Network Speed = 100MBps")
: That's the extent of the success. Boxes can't see one another (NET VIEW)
and can't ping each other (timeout)

4. Ensured NetBIOS over TCP/IP was enabled on both boxes. No change

5. Added NetBEUI protocol to both boxes. No luck. No change. I tried this
both in addition to preserving the IP stack and also after having wiped out
the IP stack on both boxes. Nothing - nada.

6. I've tried all of the above in concert with logging into the laptop with
a LOCAL administrator account that also exists on the home PC ("CommonID").

7. I am UNABLE to change the name of the workgroup on the home PC to be the
same as the name of the laptop's domain because the format of my company's
domain names (...bless their hearts) is xxxx.xxxxxx.xxxxx.com which is too
long a name to fit in the little box provided for the name of workgroup. Not
sure this would make a difference - I'm inclined to think not, given that the
basic ping test failed.

I'm stuck. People at work are useless - colleagues are not IT proficient
(... nor am I really)

nbtstat is not available on the office laptop (...these machines are built
off an image - I wouldn't be surprised if most support programs were not
provided), so if anyone will reply with a request to run some stats, please
also let me know if I can port the versions that are on the home PC over to
the laptop (i.e. do these programs operate independant of the operating
system version) - I have not tried this, and probably wouldn't know how to
read the output anyway.

Help - and thanks for any help !

HWH
 
C

Chuck

Hello - I think from reading prior posts I'm going to be asking a similar
question to one that has been asked many times. Apologies if this is going to
sound repetitive.

I'm trying to permit the exchange of data between my office PC (a W2K laptop
that is a member of a corporate domain) and my home PC (a standalone XP Home
Edition PC configured as a workgroup member).

Connection is via a crossover cable. No routers to content with.

Here's what I know about the office laptop:
- DHCP enabled
- I have admin rights either via a cached account on the domain or through
an account local to the PC (both are available)
- I'm quite certain there are some policy restrictions that the laptop is
adhering to (by virtue of its membership in the corporate domain) but
wouldn't know where to research what they consist of. Hopefully this is not
an issue.

Things I've tried:

1. The obvious first thing I did was to enabled File and Print sharing on
the home PC, and to actually set-up a share on both boxes (open to everyone,
no restrictions).

2. Disabled the XP firewall completely.

3. Programmed a static IP of a.b.c.1 and a gateway of a.b.c.1 on the home
PC; programmed a static IP of a.b.c.2 and a gateway of a.b.c.1 on the office
PC (... this is suboptimal - I would really rather avoid having to do this,
since it involves switching things back and forth every time I want to bring
the laptop home)

Result ->
: Office PC and Home PC both recognize each other when the cable is
connected ("Local Area Network Speed = 100MBps")
: That's the extent of the success. Boxes can't see one another (NET VIEW)
and can't ping each other (timeout)

4. Ensured NetBIOS over TCP/IP was enabled on both boxes. No change

5. Added NetBEUI protocol to both boxes. No luck. No change. I tried this
both in addition to preserving the IP stack and also after having wiped out
the IP stack on both boxes. Nothing - nada.

6. I've tried all of the above in concert with logging into the laptop with
a LOCAL administrator account that also exists on the home PC ("CommonID").

7. I am UNABLE to change the name of the workgroup on the home PC to be the
same as the name of the laptop's domain because the format of my company's
domain names (...bless their hearts) is xxxx.xxxxxx.xxxxx.com which is too
long a name to fit in the little box provided for the name of workgroup. Not
sure this would make a difference - I'm inclined to think not, given that the
basic ping test failed.

I'm stuck. People at work are useless - colleagues are not IT proficient
(... nor am I really)

nbtstat is not available on the office laptop (...these machines are built
off an image - I wouldn't be surprised if most support programs were not
provided), so if anyone will reply with a request to run some stats, please
also let me know if I can port the versions that are on the home PC over to
the laptop (i.e. do these programs operate independant of the operating
system version) - I have not tried this, and probably wouldn't know how to
read the output anyway.

Help - and thanks for any help !

HWH

Assuming that you have physical connectivity ("Local Area Network Speed =
100MBps"), you now need to setup logical connectivity (TCP/IP). Your "a.b.c.1"
etc crap gave me a headache. You're going to have to trust us with details if
you want real help.
<http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html>
http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html

Work from the bottom up please. TMI above.
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html

Start by getting the cross-over cable working, and tested.
<http://nitecruzr.blogspot.com/2005/07/connecting-two-computers-with.html>
http://nitecruzr.blogspot.com/2005/07/connecting-two-computers-with.html

After you get TCP/IP and pinging working, then get rid of NetBEUI, and get
NetBIOS Over TCP/IP working and tested. You can do that using browstat on both
computers.
<http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html>
http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html

After you have NBT working and tested, get file sharing working.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html
 
H

HWH

Additional information:

Browstat from W2K box:

Status for domain NA on transport
\Device\Nbf_NdisWanNbfOut{F01F24A2-63FD-4ADA-B7AC-7777719F9D10}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for domain NA on transport
\Device\Nbf_NdisWanNbfOut{56A93C0D-F0F6-4BA0-90FF-8CF83138498E}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for domain NA on transport
\Device\Nbf_NdisWanNbfOut{6A858669-AEAB-41C0-8032-D077022E22B8}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for domain NA on transport
\Device\Nbf_NdisWanNbfIn{FA8EF9FD-277C-4402-AE71-41E2650C21E4}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for domain NA on transport
\Device\Nbf_NdisWanNbfIn{97CB9309-443B-49C7-9377-9B91B6D8360E}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for domain NA on transport
\Device\Nbf_NdisWanNbfIn{61062835-D56F-4B8C-B31C-E1A808102445}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for domain NA on transport \Device\NwlnkNb
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for domain NA on transport
\Device\Nbf_{019F47D8-5BE3-430D-8D95-F3485A4A0CCB}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for do! main NA on transport
\Device\NetBT_Tcpip_{019F47D8-5BE3-430D-8D95-F3485A4A0CCB}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


---


Browstat from XP box:

Status for domain WORKGROUP on transport
\Device\Nbf_NdisWanNbfOut{DD16CA83-F599-44C1-A020-89630366CF7C}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain WORKGROUP on transport
\Device\Nbf_NdisWanNbfIn{93D6A8A4-6859-4073-8934-A11010D174C1}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain WORKGROUP on transport
\Device\Nbf_NdisWanNbfOut{9B1EF78C-0022-4D44-8726-040ED71F0EDD}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain WORKGROUP on transport
\Device\Nbf_NdisWanNbfOut{35CF8CE4-2C4C-4530-BAA6-0357DBF0003D}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain WORKGROUP on transport
\Device\Nbf_NdisWanNbfIn{4FFA94FE-2047-4C8B-877B-23D9C27A5204}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain WORKGROUP on transport
\Device\Nbf_NdisWanNbfIn{932FA9A1-1EB1-4F2C-8C99-88493934A52F}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain WORKGROUP on transport
\Device\Nbf_{EB348CCE-3EED-44D1-ADF4-178F01FBE018}
Browsing is active on domain.
Master browser name is: HOME01
Master browser is running build 2600
1 backup servers retrieved from master HOME01
\\HEAPY01
There are 1 servers in domain WORKGROUP on transport
\Device\Nbf_{EB348CCE-3EED-44D1-ADF4-178F01FBE018}
There are 1 domains in domain WORKGROUP on transport
\Device\Nbf_{EB348CCE-3EED-44D1-ADF4-178F01FBE018}


Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{EB348CCE-3EED-44D1-ADF4-178F01FBE018}
Browsing is active on domain.
Master browser name is: HOME01
Master browser is running build 2600
1 backup servers retrieved from master HOME01
\\HEAPY01
There are 1 servers in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{EB348CCE-3EED-44D1-ADF4-178F01FBE018}
There are 1 domains in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{EB348CCE-3EED-44D1-ADF4-178F01FBE018}



===========
===========
 
C

Chuck

Additional information:

Browstat from W2K box:

Status for domain NA on transport
\Device\Nbf_NdisWanNbfOut{F01F24A2-63FD-4ADA-B7AC-7777719F9D10}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for domain NA on transport
\Device\Nbf_NdisWanNbfOut{56A93C0D-F0F6-4BA0-90FF-8CF83138498E}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for domain NA on transport
\Device\Nbf_NdisWanNbfOut{6A858669-AEAB-41C0-8032-D077022E22B8}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for domain NA on transport
\Device\Nbf_NdisWanNbfIn{FA8EF9FD-277C-4402-AE71-41E2650C21E4}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for domain NA on transport
\Device\Nbf_NdisWanNbfIn{97CB9309-443B-49C7-9377-9B91B6D8360E}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for domain NA on transport
\Device\Nbf_NdisWanNbfIn{61062835-D56F-4B8C-B31C-E1A808102445}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for domain NA on transport \Device\NwlnkNb
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for domain NA on transport
\Device\Nbf_{019F47D8-5BE3-430D-8D95-F3485A4A0CCB}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.

Status for do! main NA on transport
\Device\NetBT_Tcpip_{019F47D8-5BE3-430D-8D95-F3485A4A0CCB}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


---


Browstat from XP box:

Status for domain WORKGROUP on transport
\Device\Nbf_NdisWanNbfOut{DD16CA83-F599-44C1-A020-89630366CF7C}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain WORKGROUP on transport
\Device\Nbf_NdisWanNbfIn{93D6A8A4-6859-4073-8934-A11010D174C1}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain WORKGROUP on transport
\Device\Nbf_NdisWanNbfOut{9B1EF78C-0022-4D44-8726-040ED71F0EDD}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain WORKGROUP on transport
\Device\Nbf_NdisWanNbfOut{35CF8CE4-2C4C-4530-BAA6-0357DBF0003D}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain WORKGROUP on transport
\Device\Nbf_NdisWanNbfIn{4FFA94FE-2047-4C8B-877B-23D9C27A5204}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain WORKGROUP on transport
\Device\Nbf_NdisWanNbfIn{932FA9A1-1EB1-4F2C-8C99-88493934A52F}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


Status for domain WORKGROUP on transport
\Device\Nbf_{EB348CCE-3EED-44D1-ADF4-178F01FBE018}
Browsing is active on domain.
Master browser name is: HOME01
Master browser is running build 2600
1 backup servers retrieved from master HOME01
\\HEAPY01
There are 1 servers in domain WORKGROUP on transport
\Device\Nbf_{EB348CCE-3EED-44D1-ADF4-178F01FBE018}
There are 1 domains in domain WORKGROUP on transport
\Device\Nbf_{EB348CCE-3EED-44D1-ADF4-178F01FBE018}


Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{EB348CCE-3EED-44D1-ADF4-178F01FBE018}
Browsing is active on domain.
Master browser name is: HOME01
Master browser is running build 2600
1 backup servers retrieved from master HOME01
\\HEAPY01
There are 1 servers in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{EB348CCE-3EED-44D1-ADF4-178F01FBE018}
There are 1 domains in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{EB348CCE-3EED-44D1-ADF4-178F01FBE018}



===========
===========

Is this the same setup as described in "Can't connect office laptop to home PC"?
If so, please remove NetBEUI from the setup. You do not need it complicating
things. Next, let's go back to the ping diagnostics in the other thread.
 

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