i want to connect my laptop to my desktop, so i can send files to it(the desk top) so i can burn the files to a cd.
My laptop has no floppy or burnner >< thus the major need for help. I also want to clean my laptop up(delete and get rid of stuff).
I have the cat5e crossover wire...
But what do i do now?
any place w/ info would be awesome. This is day 3 of my trying to get this to work ._.
- Forums
- Cross Site
- Computer Hardware & Troubleshooting
- i need some comp help. (was forum=28)
i need some comp help. (was forum=28)Follow
I'm not very well versed on connecting them directly, but can't you enable file sharing and do it over your internet connection? It'll probably be slower but that's how I transfer files between my laptop and desktop.
yea that would work. but you cant do that on dial up (dialup ftw!)
Hmmm... Well. There's the "sane" way of doing that, which takes a bit of knowledge about networking and about 30 second of work. And then there's the "MS way", which requires no knowledge about networking, but might take hours of head pounding annoyance...
Assuming both systems are running a MS os, you should be able to just connect the cable between the two (assuming it is a crossover cable). Then go play around with the interface settings in some obscure and inexplicable way, hoping to find the correct "wizard" that'll allow them to talk to eachother. Then set up file sharing and simply copy the files from one to the other.
Vague? Yeah. I've yet to ever find anything rational about how MS does their networking. It's a hit or miss process involving a lot of guesswork about what non-standard terminology some MS writer thought might be a "simpler" description of something.
On a *nix system, it would require typing 4 commands:
On system one:
ifconfig eth0 192.168.0.1 up
exportfs -i <path to files>
On system two:
ifconfig eth0 192.168.0.2 up
mount 192.168.0.1:<path to files> <some local directory>
Copy files from the location you mounted the remote directory to, to where you want the files to go.
But that's apparently waaaaaaay too difficult, so you'll get to fiddle with random gui nonsense until eventualy *maybe* it'll work...
Assuming both systems are running a MS os, you should be able to just connect the cable between the two (assuming it is a crossover cable). Then go play around with the interface settings in some obscure and inexplicable way, hoping to find the correct "wizard" that'll allow them to talk to eachother. Then set up file sharing and simply copy the files from one to the other.
Vague? Yeah. I've yet to ever find anything rational about how MS does their networking. It's a hit or miss process involving a lot of guesswork about what non-standard terminology some MS writer thought might be a "simpler" description of something.
On a *nix system, it would require typing 4 commands:
On system one:
ifconfig eth0 192.168.0.1 up
exportfs -i <path to files>
On system two:
ifconfig eth0 192.168.0.2 up
mount 192.168.0.1:<path to files> <some local directory>
Copy files from the location you mounted the remote directory to, to where you want the files to go.
But that's apparently waaaaaaay too difficult, so you'll get to fiddle with random gui nonsense until eventualy *maybe* it'll work...
King Nobby wrote:
More words please
Assuming it's Windows, you should (theoretically) be able to just hook up the cable between both computers, then go to My Network Places and pound on the F5 key until Windows decides that yes, there really IS a network there.
At that point, you can mount the drive in whichever direction you choose.
This, of course, assumes that Windows has not spontaneously de-configured itself, as it loves to do.
At that point, you can mount the drive in whichever direction you choose.
This, of course, assumes that Windows has not spontaneously de-configured itself, as it loves to do.
Isnt there a option in XP where a friend can connect directly to your comp from theirs? Dunno if you can exchange files like this it is just a thought.
On Windows...
Connect the computers through a LAN or just directly with cables, then:
Control Panel >> Network Connections >> Set up a home or small office network.
Do it on one to set up the network. It should be pretty self-explanatory. Once it's set up, it should show up for the connected computer under My Network Places.
Edit: Forgot to mention that all files to be shared need to be put in the Shared folder, because that's what you access through the network that you just set up.
Edited, Oct 23rd 2006 at 6:21pm PDT by mrquark
Connect the computers through a LAN or just directly with cables, then:
Control Panel >> Network Connections >> Set up a home or small office network.
Do it on one to set up the network. It should be pretty self-explanatory. Once it's set up, it should show up for the connected computer under My Network Places.
Edit: Forgot to mention that all files to be shared need to be put in the Shared folder, because that's what you access through the network that you just set up.
Edited, Oct 23rd 2006 at 6:21pm PDT by mrquark
Scholar
38 posts
IMHO buying a Jump Drive would be the best way...Though I am lazy like that.
gbaji wrote:
On system one:
ifconfig eth0 192.168.0.1 up
exportfs -i <path to files>
On system two:
ifconfig eth0 192.168.0.2 up
mount 192.168.0.1:<path to files> <some local directory>
Copy files from the location you mounted the remote directory to, to where you want the files to go.
But that's apparently waaaaaaay too difficult, so you'll get to fiddle with random gui nonsense until eventualy *maybe* it'll work...
ifconfig eth0 192.168.0.1 up
exportfs -i <path to files>
On system two:
ifconfig eth0 192.168.0.2 up
mount 192.168.0.1:<path to files> <some local directory>
Copy files from the location you mounted the remote directory to, to where you want the files to go.
But that's apparently waaaaaaay too difficult, so you'll get to fiddle with random gui nonsense until eventualy *maybe* it'll work...
It is a Proven Fact that entering commands on a command line makes god hate you. I read that somewhere.
few things to list:
1. as mentioned above you need to tell MS to setup a home network. no you do not. you can do it manually and be better off for it.
2. verify that the crossover cable is working. most NICs have a green light on them to indicate they are connected if not, you can go into "My Network Places" by right clicking and going to properties. that should show you a list of what is connected and what is not.
3. set a static IP on both computers that are in the same IP scheme, but NOT the same IP.
example: desktop = IP 192.168.10.1 with a subnet 255.255.255.0 gateway = 192.168.10.1 yes the gateway is it self.
laptop = IP 192.168.10.2 same info for the rest as the desktop.
4. you need to have a shared folder if you are not connected to the INTERNET at this time it is safe enough to allow all/all for access.
5. you might need to reboot BOTH computers, this is windows we are talking about and even with the static IPs MS is notorious for ******** up simple network connections like this.
6. navigate via explorer (not IE) with the following command: //192.168.10.1/sharefolder_name
hit enter and go to town. you should then be able to click and drag the files from the laptop to the desktop, or better yet you could set the share folder up on your laptop, get to that folder (change the IP address from above) and just burn the files directly via the LAN. as long as both computers have 10/100 NICs that should be fast enough to NOT fail the burn.
good luck and yes these kinds of things are why i get paid $75 an hour for home networks.
1. as mentioned above you need to tell MS to setup a home network. no you do not. you can do it manually and be better off for it.
2. verify that the crossover cable is working. most NICs have a green light on them to indicate they are connected if not, you can go into "My Network Places" by right clicking and going to properties. that should show you a list of what is connected and what is not.
3. set a static IP on both computers that are in the same IP scheme, but NOT the same IP.
example: desktop = IP 192.168.10.1 with a subnet 255.255.255.0 gateway = 192.168.10.1 yes the gateway is it self.
laptop = IP 192.168.10.2 same info for the rest as the desktop.
4. you need to have a shared folder if you are not connected to the INTERNET at this time it is safe enough to allow all/all for access.
5. you might need to reboot BOTH computers, this is windows we are talking about and even with the static IPs MS is notorious for ******** up simple network connections like this.
6. navigate via explorer (not IE) with the following command: //192.168.10.1/sharefolder_name
hit enter and go to town. you should then be able to click and drag the files from the laptop to the desktop, or better yet you could set the share folder up on your laptop, get to that folder (change the IP address from above) and just burn the files directly via the LAN. as long as both computers have 10/100 NICs that should be fast enough to NOT fail the burn.
good luck and yes these kinds of things are why i get paid $75 an hour for home networks.
Lol. You know how long it took me to figure out how to set up a static IP address on XP? About 3 hours. You know why? Because MS can't seem to use any kind of "normal" terminology...
IIRC, on a brand new system with nothing configured, you have to run the "new network connection" wizard. You have to navigate the byzantine set of options that have no rhyme or reason to them to eventually configure a lan connection (and avoid doing weird stuff like creating a home network by mistake). Then you have to right click that lan connection and go to properties, then select the tcp/ip device and hit the properties button and *then* finally you can configure the interface.
No other operating system in the world makes something so simple into something so complex. For some bizarre reason MS wants to create an abstraction layer between the user and the interface devices themselves, presumably to make it "easier" to manage networking. And certainly, if you have a single interface and connect directly to a dhcp-ready network, it'll somewhat automatically "do the right thing". But they didn't really need those extra layers to do that. You'd think a "home network" would involve actually setting up a private net address range for home use, but apparently MS conflates that into a whole bunch of security settings and shared stuff that doesn't work if you don't *also* configure an interface correctly in the first place.
If they wanted to make it "simple", they'd just have a pop up that would show every physical network device on the system. Then allow you to select each/any device and then configure them. Gee! That would be simple, right? Or is clicking on "Lan Card 0" and then setting it to static or dynamic IP and such that hard? I honestly have no clue why they make this so complicated. It's not like they have increased functionality one bit...
IIRC, on a brand new system with nothing configured, you have to run the "new network connection" wizard. You have to navigate the byzantine set of options that have no rhyme or reason to them to eventually configure a lan connection (and avoid doing weird stuff like creating a home network by mistake). Then you have to right click that lan connection and go to properties, then select the tcp/ip device and hit the properties button and *then* finally you can configure the interface.
No other operating system in the world makes something so simple into something so complex. For some bizarre reason MS wants to create an abstraction layer between the user and the interface devices themselves, presumably to make it "easier" to manage networking. And certainly, if you have a single interface and connect directly to a dhcp-ready network, it'll somewhat automatically "do the right thing". But they didn't really need those extra layers to do that. You'd think a "home network" would involve actually setting up a private net address range for home use, but apparently MS conflates that into a whole bunch of security settings and shared stuff that doesn't work if you don't *also* configure an interface correctly in the first place.
If they wanted to make it "simple", they'd just have a pop up that would show every physical network device on the system. Then allow you to select each/any device and then configure them. Gee! That would be simple, right? Or is clicking on "Lan Card 0" and then setting it to static or dynamic IP and such that hard? I honestly have no clue why they make this so complicated. It's not like they have increased functionality one bit...
King Nobby wrote:
More words please
17 posts
cover it with a thin layer of tin foil and 1 full layer of ducktape now put it in the microwave or oven and ur good to go
Edited, Oct 25th 2006 at 9:03pm PDT by arloughlen
Edited, Oct 25th 2006 at 9:03pm PDT by arloughlen
Mindel wrote:
gbaji wrote:
On system one:
ifconfig eth0 192.168.0.1 up
exportfs -i <path to files>
On system two:
ifconfig eth0 192.168.0.2 up
mount 192.168.0.1:<path to files> <some local directory>
Copy files from the location you mounted the remote directory to, to where you want the files to go.
But that's apparently waaaaaaay too difficult, so you'll get to fiddle with random gui nonsense until eventualy *maybe* it'll work...
ifconfig eth0 192.168.0.1 up
exportfs -i <path to files>
On system two:
ifconfig eth0 192.168.0.2 up
mount 192.168.0.1:<path to files> <some local directory>
Copy files from the location you mounted the remote directory to, to where you want the files to go.
But that's apparently waaaaaaay too difficult, so you'll get to fiddle with random gui nonsense until eventualy *maybe* it'll work...
It is a Proven Fact that entering commands on a command line makes god hate you. I read that somewhere.
As someone who used MSDOS (2.0! ...and 6.22) and Linux, I can say that it's only using the Mac OS before OS X that makes God hate people.
gbaji wrote:
If they wanted to make it "simple", they'd just have a pop up that would show every physical network device on the system. Then allow you to select each/any device and then configure them. Gee! That would be simple, right? Or is clicking on "Lan Card 0" and then setting it to static or dynamic IP and such that hard? I honestly have no clue why they make this so complicated. It's not like they have increased functionality one bit...
this made me laugh a bit... Yes it is simple, but ONLY if you know what you are doing unlike the OS you are describing very clear to those of us who have used that OS.
anyways. yes with XP things got very muddy in how to configure things and the bloody network wizard with XP is a joke. win2k was very very very simple, much more so then anything win9x line had and much more robust then winNT, but still nothing compared to OSx or Linux for that matter.
oh well the above info should get him pointed in the right direction, or he just needs to go out and buy a 12G USB device, or invest in an external harddrive and case that connects either/both USB2.0 and FireWire and be done with it.
Recent Visitors: 6
All times are in CST
Anonymous Guests (6)
- Forums
- Cross Site
- Computer Hardware & Troubleshooting
- i need some comp help. (was forum=28)
© 2025 Fanbyte LLC