connecting 2 pcs belonging to 2 different domains

[Guest]

Thanks, in advance, for any suggestions.

I have an OLD laptop running XP that belongs to a domain called IAC.

I have a NEW laptop running XP that belongs to a different domain called AD.

There appears to be no common network drives/folders shared by IAC and AD
where I could temporarily stash my files while I move them from OLD to NEW.

I have administrator rights on both machines but am not a network
administrator.

I need to transfer 20gigs of data from OLD to NEW.

Because I cannot create or join workgroups on either machine (because they
already belong to domains), I have not been able to connect them with a
crossover cable. [I connected them, logged in as 'THIS COMPUTER", set static
IPs and Subnet masks for each, but cannot ping the other machine. All
instructions say that I must join each to the same workgroup for the
networkign to work. But of course, I can't join a workgroup because each
machine already belongs to a domain.]

My question:
Is there anyway to connect the two machines directly to transfer the files
from OLD to NEW that does not require joining/creating a common workgroup?
Remember, I am using XP and each machine belongs to a different domain over
which I have no control. (Of course, besides FTPing to my directory and then
downloading to the new machine.)

Am I completely dependent on my network administrator to handle this? (I
anticipate a 2 week wait before he can get around to it.)

Thanks! md

 

[Guest]

Sorry. Forgot to add that I disabled XP firewall and still not able to ping
from one to the other. No other firewalls running.
md

 

[Chuck]

Thanks, in advance, for any suggestions.

I have an OLD laptop running XP that belongs to a domain called IAC.

I have a NEW laptop running XP that belongs to a different domain called AD.

There appears to be no common network drives/folders shared by IAC and AD
where I could temporarily stash my files while I move them from OLD to NEW.

I have administrator rights on both machines but am not a network
administrator.

I need to transfer 20gigs of data from OLD to NEW.

Because I cannot create or join workgroups on either machine (because they
already belong to domains), I have not been able to connect them with a
crossover cable. [I connected them, logged in as 'THIS COMPUTER", set static
IPs and Subnet masks for each, but cannot ping the other machine. All
instructions say that I must join each to the same workgroup for the
networkign to work. But of course, I can't join a workgroup because each
machine already belongs to a domain.]

My question:
Is there anyway to connect the two machines directly to transfer the files
from OLD to NEW that does not require joining/creating a common workgroup?
Remember, I am using XP and each machine belongs to a different domain over
which I have no control. (Of course, besides FTPing to my directory and then
downloading to the new machine.)

Am I completely dependent on my network administrator to handle this? (I
anticipate a 2 week wait before he can get around to it.)

Thanks! md

Michelle,

Please start by understanding the difference between pinging, domain / workgroup
membership, and ability to network two computers.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html>

Pinging is a low level activity, and pinging by ip address will work if you can
configure both computers to be on the same subnet, or if both computers are
setup for DHCP and both self assign APIPA addresses. Pinging by name will work
if both computers have compatible Node Type.

When you ping each from the other, how are you pinging - by name or by ip
address? Are both computers in the same subnet when you ping? Run "ipconfig"
on the 2, and see what ip address / subnet mask you get, and list them here.
That will tell us what you need to do next.

Once you get pinging to work, we'll work on the actual connecting.

 

[Guest]

AhA....
Thanks, Chuck. One step closer to identifying the problem. Still don't know
the solution.

On both machines, regardless of whether I am logged in with the Domain user
or the This Computer user (I tried both for good measure, and both have admin
rights on the machine for what its worth), when I run ipconfig, it tells me
that the Media State.....is.....Media disconnected.

This despite the fact that the icons on both machines in Network Connections
say 'connected'. If I right-click, and look at the properties on both OLD
(IAC domain) and NEW (AD domain), I've set the TCP/IP to Static IPs
(192.168.0.1 for NEW and 192.168.0.2 for OLD) and Subnet Masks are both the
same (255.255.255.0).

Could it be as simple as the crossover cable isn't good or isn't really a
crossover? I should admit that the undergraduate networking assistant made
the cable for me (I'm a prof) and maybe he didn't crimp it right, or didn't
do the crossover right.

I tried to ping 192.168.0.1 from OLD to NEW. Just to see if they were
connected.

So does that mean that pinging has nothing to with (or works at a lower
level than) workgrouping? I just assumed the network administrator by virtue
of adding these machines to the domain would be able to micromanage what I
can do with them, and restrict not only my ability to unjoin the domain but
also set up a mini-network between 2 machines assigned to different domains.

Thanks again.

 

[Chuck]

AhA....
Thanks, Chuck. One step closer to identifying the problem. Still don't know
the solution.

On both machines, regardless of whether I am logged in with the Domain user
or the This Computer user (I tried both for good measure, and both have admin
rights on the machine for what its worth), when I run ipconfig, it tells me
that the Media State.....is.....Media disconnected.

This despite the fact that the icons on both machines in Network Connections
say 'connected'. If I right-click, and look at the properties on both OLD
(IAC domain) and NEW (AD domain), I've set the TCP/IP to Static IPs
(192.168.0.1 for NEW and 192.168.0.2 for OLD) and Subnet Masks are both the
same (255.255.255.0).

Could it be as simple as the crossover cable isn't good or isn't really a
crossover? I should admit that the undergraduate networking assistant made
the cable for me (I'm a prof) and maybe he didn't crimp it right, or didn't
do the crossover right.

I tried to ping 192.168.0.1 from OLD to NEW. Just to see if they were
connected.

So does that mean that pinging has nothing to with (or works at a lower
level than) workgrouping? I just assumed the network administrator by virtue
of adding these machines to the domain would be able to micromanage what I
can do with them, and restrict not only my ability to unjoin the domain but
also set up a mini-network between 2 machines assigned to different domains.

Thanks again.

Michelle,

The absolute last thing I would ever play with is a hand made cross-over cable.
Please go buy a good cable. If you're working on any network problem, always
always start with a commercial grade pre-made and tested cable!
<http://nitecruzr.blogspot.com/2005/04/making-your-own-ethernet-cables-is-not.html>

The only need you have for administrative access to each computer is:
1) To change the ip address and put both computers on the same subnet.
2) To set permissioning up between the two computers.
<http://nitecruzr.blogspot.com/2005/07/windows-networking.html>

If you can get both computers pinging each other by name, then do Start - Run -
"\\OtherComputerName", or "\\OtherComputerIPAddress", and you'll see the shares
offered by the other computer (substitute name or address of other computer).

But first:
1) Take the Ethernet cable you're using (if it was indeed handmade) and tie it
into a knot.
2) Go to the nearest computer store and buy a cross-over cable.

 

[Guest]

Thanks, Chuck. Will do. If it doesn't work with a good cable tomorrow, I'll
be back with a follow-up.
Best, md

 

[Chuck]

Thanks, Chuck. Will do. If it doesn't work with a good cable tomorrow, I'll
be back with a follow-up.
Best, md

Michelle,

Please do let us know how it turns out - good or bad.

 

[Richard G. Harper]

Just a suggestion - why not eschew the network and use some other means of
transferring files like an external USB hard drive?

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[Guest]

Good suggestion, but my external harddrives aren't available right now. I'd
be back asking for the OIT guy.

Ok. I can ping back and forth. But still don't know how to 'see' one pc from
the other. I've gone to the My Network Connections and when I click on the
domain for the other machine (i.e., click IAC when I'm on the AD machine), it
tells me that I don't have network permission to use those resources.

Really, I'd move all the files using the cmd interface if that's easier. I
don't need a fancy connection, just fast, since we're talking about 20gig of
files.

Really specific next steps would be great, Chuck. I'll add you to my
blogroll if this works! md

Just a suggestion - why not eschew the network and use some other means of
transferring files like an external USB hard drive?

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Thanks, in advance, for any suggestions.

I have an OLD laptop running XP that belongs to a domain called IAC.

I have a NEW laptop running XP that belongs to a different domain called
AD.

There appears to be no common network drives/folders shared by IAC and AD
where I could temporarily stash my files while I move them from OLD to
NEW.

I have administrator rights on both machines but am not a network
administrator.

I need to transfer 20gigs of data from OLD to NEW.

Because I cannot create or join workgroups on either machine (because they
already belong to domains), I have not been able to connect them with a
crossover cable. [I connected them, logged in as 'THIS COMPUTER", set
static
IPs and Subnet masks for each, but cannot ping the other machine. All
instructions say that I must join each to the same workgroup for the
networkign to work. But of course, I can't join a workgroup because each
machine already belongs to a domain.]

My question:
Is there anyway to connect the two machines directly to transfer the files
from OLD to NEW that does not require joining/creating a common workgroup?
Remember, I am using XP and each machine belongs to a different domain
over
which I have no control. (Of course, besides FTPing to my directory and
then
downloading to the new machine.)

Am I completely dependent on my network administrator to handle this? (I
anticipate a 2 week wait before he can get around to it.)

Thanks! md

 

[Guest]

Oh, and the OLD machine has a USB 1.0 so I imagine 20 gigs would take ALL
day, no?

Good idea, though, and I might consider it if I had my drives available.

 

[Chuck]

Just a suggestion - why not eschew the network and use some other means of
transferring files like an external USB hard drive?

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Thanks, in advance, for any suggestions.

I have an OLD laptop running XP that belongs to a domain called IAC.

I have a NEW laptop running XP that belongs to a different domain called
AD.

There appears to be no common network drives/folders shared by IAC and AD
where I could temporarily stash my files while I move them from OLD to
NEW.

I have administrator rights on both machines but am not a network
administrator.

I need to transfer 20gigs of data from OLD to NEW.

Because I cannot create or join workgroups on either machine (because they
already belong to domains), I have not been able to connect them with a
crossover cable. [I connected them, logged in as 'THIS COMPUTER", set
static
IPs and Subnet masks for each, but cannot ping the other machine. All
instructions say that I must join each to the same workgroup for the
networkign to work. But of course, I can't join a workgroup because each
machine already belongs to a domain.]

My question:
Is there anyway to connect the two machines directly to transfer the files
from OLD to NEW that does not require joining/creating a common workgroup?
Remember, I am using XP and each machine belongs to a different domain
over
which I have no control. (Of course, besides FTPing to my directory and
then
downloading to the new machine.)

Am I completely dependent on my network administrator to handle this? (I
anticipate a 2 week wait before he can get around to it.)

Thanks! md

Good suggestion, but my external harddrives aren't available right now. I'd
be back asking for the OIT guy.

Ok. I can ping back and forth. But still don't know how to 'see' one pc from
the other. I've gone to the My Network Connections and when I click on the
domain for the other machine (i.e., click IAC when I'm on the AD machine), it
tells me that I don't have network permission to use those resources.

Really, I'd move all the files using the cmd interface if that's easier. I
don't need a fancy connection, just fast, since we're talking about 20gig of
files.

Really specific next steps would be great, Chuck. I'll add you to my
blogroll if this works! md

Michelle,

OK, if you have connectivity (and name resolution?), you now have 2 choices:
1) With both computers in the same workgroup, start the Browser service on one
(just one please), so you'll be able to "see" each computer in Network
Neighborhood.
<http://nitecruzr.blogspot.com/2005/06/services-running-on-your-computer.html>
2) Forget about the browser, and map shares directly.
<http://nitecruzr.blogspot.com/2005/07/windows-networking.html#Total>

In your case, I'd go with #2. Want to use the browser? Start by running
browstat on both computers.
<http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html>

Please let us know if any of these suggestions are of any help. What you learn
may help others in the future, and that's the purpose of these forums.

 

[Guest]

Michelle,

OK, if you have connectivity (and name resolution?), you now have 2 choices:
1) With both computers in the same workgroup, start the Browser service on one
(just one please), so you'll be able to "see" each computer in Network
Neighborhood.
<http://nitecruzr.blogspot.com/2005/06/services-running-on-your-computer.html>

This sounds nice, but since the PCs belong to two different domains, I can't
join them to the same workgroup. I tried this initially, by joining IAC to
the AD workgroup, but it won't let me b/c IAC already belongs to a domain
(IAC).

2) Forget about the browser, and map shares directly.
<http://nitecruzr.blogspot.com/2005/07/windows-networking.html#Total>

I tried this. I can ping from OLD to NEW using the IP address of NEW. When
I type \\192.168.0.1 (representing NEW) from the cmd prompt on OLD, it tells
me....(let's see if I can remember) something about a bad filename, could not
find....directory path no good....something like that.

In the meantime, I have found a PC in our undergrad lab that I can use to
log in to both the IAC (OLD) and AD (NEW) domains, so I'm thinking it may be
easier to copy files from OLD to my directory on IAC domain server, then
download to the c drive of that PC, then log out, log in to AD, and copy the
files to the AD domain, and then copy down to my NEW pc. Sounds complicated,
but I'm not having luck with the network. And it's essentially like the
suggestion of using an external USB drive. The downside is that there will be
my file residue on both the servers and the PC drive, and since I teach at a
Tech university, I don't like the idea of having file residue (of exams,
grades, etc.) on a lab machine.

Thanks again, Chuck.

 

[Chuck]

This sounds nice, but since the PCs belong to two different domains, I can't
join them to the same workgroup. I tried this initially, by joining IAC to
the AD workgroup, but it won't let me b/c IAC already belongs to a domain
(IAC).


I tried this. I can ping from OLD to NEW using the IP address of NEW. When
I type \\192.168.0.1 (representing NEW) from the cmd prompt on OLD, it tells
me....(let's see if I can remember) something about a bad filename, could not
find....directory path no good....something like that.

In the meantime, I have found a PC in our undergrad lab that I can use to
log in to both the IAC (OLD) and AD (NEW) domains, so I'm thinking it may be
easier to copy files from OLD to my directory on IAC domain server, then
download to the c drive of that PC, then log out, log in to AD, and copy the
files to the AD domain, and then copy down to my NEW pc. Sounds complicated,
but I'm not having luck with the network. And it's essentially like the
suggestion of using an external USB drive. The downside is that there will be
my file residue on both the servers and the PC drive, and since I teach at a
Tech university, I don't like the idea of having file residue (of exams,
grades, etc.) on a lab machine.

Thanks again, Chuck.

If you could Ping NEW from OLD, but couldn't display its shares, then you have
either a firewall or a restrictanonymous issue.
Misconfigured / overlooked firewalls:
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
Registry setting restrictanonymous:
<http://nitecruzr.blogspot.com/2005/07/restrictanonymous-and-your-server.html>

But, as long as you can find a solution, it's a one time deal, so go with it.
Thanks for letting us know.

 

[Guest]

If you could Ping NEW from OLD, but couldn't display its shares, then you
have

either a firewall or a restrictanonymous issue.
Misconfigured / overlooked firewalls:
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
Registry setting restrictanonymous:
<http://nitecruzr.blogspot.com/2005/07/restrictanonymous-and-your-server.html>

But, as long as you can find a solution, it's a one time deal, so go with it.
Thanks for letting us know.

Thanks, again, for your help. I'm fairly certain it wasn't a firewall issue
since the NEW machine did not have a 3rd party firewall installed and the WIN
firewall was disabled (...which reminds me that I need to enable it....). I
read your blog about the registry settings, but did not investigate further.

It took about 5+ hours but I finally was able to transfer the files using
the File Transfer Wizard. Most of the time was the OLD and the NEW machines
either compressing or decommpressing the files. I put the wizard files in a
shared folder on OLD. It took about 45 minutes to download the wizard files
(13 gigs) to the lab PC while both OLD and the lab PC were logged on to the
IAC network. It then took another 45 minutes to upload the wizard files to
my active directory on the AD network. When I logged in NEW to the AD the
first time, it took awhile to sync the files (about 25 min), but then I was
able to use the transfer wizard to install the files from the active
directory on AD.

Not the most elegant of work-arounds, but by Friday 5pm, I had finished!
(Just about the time the IT guy stopped by who could have just set up NEW to
log in to both domains.... ) Thanks again. Will recommend your blog to my
dad who does small network IT support.

 

[Chuck]

Thanks, again, for your help. I'm fairly certain it wasn't a firewall issue
since the NEW machine did not have a 3rd party firewall installed and the WIN
firewall was disabled (...which reminds me that I need to enable it....). I
read your blog about the registry settings, but did not investigate further.

It took about 5+ hours but I finally was able to transfer the files using
the File Transfer Wizard. Most of the time was the OLD and the NEW machines
either compressing or decommpressing the files. I put the wizard files in a
shared folder on OLD. It took about 45 minutes to download the wizard files
(13 gigs) to the lab PC while both OLD and the lab PC were logged on to the
IAC network. It then took another 45 minutes to upload the wizard files to
my active directory on the AD network. When I logged in NEW to the AD the
first time, it took awhile to sync the files (about 25 min), but then I was
able to use the transfer wizard to install the files from the active
directory on AD.

Not the most elegant of work-arounds, but by Friday 5pm, I had finished!
(Just about the time the IT guy stopped by who could have just set up NEW to
log in to both domains.... ) Thanks again. Will recommend your blog to my
dad who does small network IT support.

The FTW is a trip isn't it? I have found that the learning curve can be pretty
scary sometimes. The second time should be easier for you. Glad it worked out,
and thanks for any referrals.