|
Posted by Tomás Ó hÉilidhe on January 11, 2008, 3:34 pm
If you were Registered and logged in, you could reply and use other advanced thread options
Let's say we have Mary's laptop and Brian's laptop. Brian has a 6 GB
movie file on his hard disk that he wants to transfer to Mary.
Both laptops have a NIC with an ethernet port, so obviously it would be
a good choice just to connect them with a cross-over cable and use
something like FTP or Samba to send the file across.
Anyway, before any file sending can be done, both machines have to sort
out their IP address. Because Brian and Mary regularly plug their
laptops into different networks to access the internet, they both have
DHCP set up for their NIC.
So anyway getting to the crux of it...
We hook them up with a cross-over cable. We run the DHCP client on one
of the machines. There's no response because there's no DHCP server, and
so the machine adopts a random address in the network 169.254/16. (This
is what DHCP is supposed to do if it doesn't get a response from a DHCP
server, right?)
We run the DHCP client on the other machine, and again we get a random
address in 169.254/16.
Running Windows, we then just go into network neighbourhood and viola
there's the other person's computer. Or if using FTP, we can do
"ipconfig/all" on each machine to get their IP address, then just do
ftp://169.254.5.7.
But here's what I want to ask: Is this method of using "DHCP failure"
reliable for giving the machines IP addresses with which they can
communicate? Is it really as simple as "Stick a cross-over between them
and hit DHCP on both machines"?
On another thing: Can someone please suggest a very simply free FTP
server application for Windows? I've searched a bit, even downloaded and
tried one or two of them, but they all seemed a hell of a lot more
troublesome than they should have been.
Also another thing: If you're connecting only two computers together,
would it be more efficient to use something like PPP instead of
Ethernet? I'm talking about sending 10 GB files from one machine to
another.
--
Tomás Ó hÉilidhe
|
 
| |
Posted by Albert Manfredi on January 11, 2008, 5:34 pm
If you were Registered and logged in, you could reply and use other advanced thread options
> So anyway getting to the crux of it...
>
> We hook them up with a cross-over cable. We run the DHCP client on one
> of the machines. There's no response because there's no DHCP server, and
> so the machine adopts a random address in the network 169.254/16. (This
> is what DHCP is supposed to do if it doesn't get a response from a DHCP
> server, right?)
>
> We run the DHCP client on the other machine, and again we get a random
> address in 169.254/16.
The way I would do this, if you must use TCP/IP, is to set up both
machines with a statically configured IP address first. I don't know
about this 169.254/16 subnet. It could be an address that both those
PCs had been using previously.
RFC 2131 says that if a DHCP server is unavailable, and the client is
set up to acquire its IP address via DHCP, the client can reuse its
previous IP address. However, it can only do so until the lease for
that IP address expires. Then it must stop using the IP address and it
must warn the user. At this pooint, I don't know of any legal way of
assigning IP addresses with DHCP. You have to configure manually.
But by the way, what about using netbeui instead of TCP/IP? That
should be perfect for this situation. If both machines are Windows,
and you have them on the same L2 net, this has to be the best way to
transfer files, no? Netbeui should be one of the protocol options
you're allowed to choose from, on any Windows machine. Turn it on and
see what happens.
Bert
|
|
Posted by Tomás Ó hÉilidhe on January 11, 2008, 6:07 pm
If you were Registered and logged in, you could reply and use other advanced thread options
> The way I would do this, if you must use TCP/IP, is to set up both
> machines with a statically configured IP address first.
This is what I'm currently doing at the moment... I just thought it
might be a little handier to set up some sort of "auto IP assigning"
configuration.
> I don't know
> about this 169.254/16 subnet. It could be an address that both those
> PCs had been using previously.
It's a private IP range reserved for a failed DHCP request.
> RFC 2131 says that if a DHCP server is unavailable, and the client is
> set up to acquire its IP address via DHCP, the client can reuse its
> previous IP address. However, it can only do so until the lease for
> that IP address expires. Then it must stop using the IP address and it
> must warn the user. At this pooint, I don't know of any legal way of
> assigning IP addresses with DHCP. You have to configure manually.
So it's no reliable after all then.
> But by the way, what about using netbeui instead of TCP/IP? That
> should be perfect for this situation. If both machines are Windows,
> and you have them on the same L2 net, this has to be the best way to
> transfer files, no? Netbeui should be one of the protocol options
> you're allowed to choose from, on any Windows machine. Turn it on and
> see what happens.
Forgive my ignorance, but I haven't a clue what nebeui is.
If you had two laptops and a cross-over cable, what would be the best
way of transferring files (big files in particular, such as movies)? I
know a bit about networking but not a hell of a lot. I thought it would
be best to use FTP over TCP?
--
Tomás Ó hÉilidhe
|
|
Posted by Albert Manfredi on January 11, 2008, 9:31 pm
If you were Registered and logged in, you could reply and use other advanced thread options
> > But by the way, what about using netbeui instead of TCP/IP? That
> > should be perfect for this situation. If both machines are Windows,
> > and you have them on the same L2 net, this has to be the best way to
> > transfer files, no? Netbeui should be one of the protocol options
> > you're allowed to choose from, on any Windows machine. Turn it on and
> > see what happens.
>
> Forgive my ignorance, but I haven't a clue what nebeui is.
>
> If you had two laptops and a cross-over cable, what would be the best
> way of transferring files (big files in particular, such as movies)? I
> know a bit about networking but not a hell of a lot. I thought it would
> be best to use FTP over TCP?
The way everything is automated now for network setup now, I haven't
looked for these details in years.
In WinXP, if you go to "Control Panel," then "Network Connections,"
then "Local Area Connection," click on "Properties" in the "General"
tab.
You should see a checked box for TCP/IP. You might see one also for
"Client for Microsoft Networks," and "File and Printer Sharing for
Microsoft Networks."
I think that if you have two Windows computers connected to one
another via Ethernet, you should be able to uncheck the TCP/IP box,
make sure those other two boxes are checked, and then use Windows
Explorer to see the folders on the other computer, copy and paste, and
so forth.
Netbeui is a local printer and file sharing protocol that used to be
in common use some time ago, before TCP/IP became so prevalent. It is
however not a routable protocol. For local office nets, it works fine.
Easy to set up and trouble free. I might be forgetting something, but
in older versions of Windows, it seemed like there was a box to check
that actually said netbeui.
Maybe someone on here is less vague on this netbeui stuff. To me, when
we used to use it at the office, it was a no brainer.
Bert
|
|
Posted by Rick Jones on January 11, 2008, 5:53 pm
If you were Registered and logged in, you could reply and use other advanced thread options > We hook them up with a cross-over cable. We run the DHCP client on
> one of the machines. There's no response because there's no DHCP
> server, and so the machine adopts a random address in the network
> 169.254/16. (This is what DHCP is supposed to do if it doesn't get a
> response from a DHCP server, right?)
If I am recalling things correctly, the 169.254/16 stuff isn't DHCP at
all but IPv4's version of IPv6's stateless autoconfiguration. An
entirely different set of RFC's altogether. Might all be shoved into
the same bit of client code I suppose, but I'm pretty sure they are
logically distinct.
rick jones
--
Process shall set you free from the need for rational thought.
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...
|
| Similar Threads | Posted | | Hello Guy. I just bought a cisco 7206VXR from http://www.linkwaves.com. They are seem ok. Quick shipping fedex 3 days saver for $85. I think they are great | August 16, 2006, 3:05 pm |
| DHCP traffic Blocking | May 17, 2006, 2:05 pm |
| Has anyone ever seen a crossover AUI cable? | May 20, 2005, 3:39 am |
| static routing in addition to DHCP on my router. | January 25, 2006, 11:47 pm |
| static routing in addition to DHCP on my router. | January 25, 2006, 11:47 pm |
| Problem with Crossover Cable | August 28, 2005, 1:18 pm |
| Crossover Vs. Patch Cables | March 9, 2006, 11:15 am |
| Crossover function in the standard. | June 23, 2008, 4:34 pm |
| turned off DHCP in Netgear RT314; how to turn back on? | December 30, 2005, 2:04 am |
| Disable ingress or dhcp spoofing on enterasys switches | July 31, 2007, 11:22 am |
|
|
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML site map