bagpuss
|
Networking together 2 computersMy OH has just bought a shiny new pc
We still have a lot of files, photos music library etc on the old pc we want to transfer over before we ditch it completely.
Both computers are running windows xp home edition,
The old has a now expired norton firewall (still running just not updating) and new is using xps firewall and the routers
They are both networked via a netgear 108Mps wireless router. They are both hardwired to said router
My OH can't seem to get them to talk to each other would seem necessary to transfer files about
both computers can see the internet
the new computer can see itself on the network
the only computer gets told it doesn't have permission to see/join the network when the OH tries
I have asked if it could be the router firewall but the OH doesn't think so
He thinks he needs to give the old computer some sort of permission but doesn't know how to
any suggestions
thanks
|
tahir
|
I think they both need to belong to the same workgroup
|
tahir
|
[caveman] Just burn em [/caveman]
|
bagpuss
|
| tahir wrote: | | I think they both need to belong to the same workgroup |
he has apparently tried that and it didn't seem to work
it worked fine on the new computer but the old computer when using the xp wizard was having none of it
|
Jonnyboy
|
Can you get a crossover cable and just plug them in to each other? I'm not brilliant at this but you'll probably need to share out the file folders you want to copy from (right click option)
|
MarkS
|
this is a pig of a job because windows networking is such a pos* esp on the home edition
you need the same usernames and passwords on both machines.
you need to share the folders
you need to be in the same workgroup
you may need to faff about getting the firewalls to play (possibly easier to just turn both firewalls off for the duration of this exercise)
you may need to mess about with services, browser announcing, masters etc
Or remove the hard drive from the first and put it in the new machine
as slave
*obligatory diss windows statement
|
Barefoot Andrew
|
| MarkS wrote: | | you may need to mess about with services, browser announcing, masters etc |
Just posted something about browsers, but decided it was iffy so removed it. A reword:-
Check that the "Computer Browser" service is running* - see Control Panel -> Administrative Tools -> Services and make sure that "Computer Browser" is started.
(*I'm unclear off-hand whether this service has to be running on all machines and they negotiate between them who is in charge, or whether it should be running on one machine only).
A.
|
bagpuss
|
| Barefoot Andrew wrote: | | MarkS wrote: | | you may need to mess about with services, browser announcing, masters etc |
Just posted something about browsers, but decided it was iffy so removed it. A reword:-
Check that the "Computer Browser" service is running* - see Control Panel -> Administrative Tools -> Services and make sure that "Computer Browser" is started.
(*I'm unclear off-hand whether this service has to be running on all machines and they negotiate between them who is in charge, or whether it should be running on one machine only).
A. |
it is currently running on both machines
interestingly when trying to switch on unusual ports on the netgear router we get a port in conflect type error message but the OH can't figure out what program is using the port to cause the conflict
the port in question is 3724, he wants it for WOW patch downloads
|
dougal
|
Your router firewall *only* affects external traffic. And probably only *incoming* (and not outgoing) traffic.
It does nothing to inhibit/moderate/restrict traffic on the internal network.
The problem is with the computers' setup.
Whether its to do with the computers firewalling (probable) or with the 'sharing' setup, I don't know, and can't tell from this distance.
I get the impression (from the Mac help on networking to a shared folder on a Windows machine) that the M$ "Internet Connection Firewall" prevents access to the shared folder on that machine... maybe you could check that specific in the Windoze help? | Quote: | You can set up a Windows computer to share files with other users on your network, including Mac users.
To let users connect to a Windows computer from a Mac computer, you need to share a folder on the Windows computer.
1 - If you have never set up the Windows computer for sharing, open My Network Places and follow the onscreen instructions to set up a home or small office network.
2 - To share a folder, right click the folder’s icon and choose Properties. Click the Share tab and follow the onscreen instructions.
You may need to disable the Internet Connection Firewall in the Advanced pane of the device's properties.
You may need to restart the Windows computer after setting it up. |
I'm kinda surprised that this can be so tricky under XP... No, OK, I'm not surprised...
On another well-known operating system, specifically enabling particular networking features automagically reconfigures the firewall to permit those particular services. One could almost say it was easy...
Oh, and Macs with Gigabit ethernet (ie probably most of those made in the last 10 years or so) have auto-sensing and don't need crossover cables for direct machine to machine connection. Easy? Seems that way to me.
|
bagpuss
|
looking at the netgear help does suggest disabling the XP firewall would be a good idea at least for while the transfer is being done
I fully appreciate for things like this macs are better than windows machines but my OH is a gamer and macs and most computer games don't work togther and those which do he would need to buy new copys of so I was never going to convince him onto a mac (plus we wouldn't of got this spec for just over £500 with apple)
|
orangepippin
|
I would disable the firewalls on both PCs to start with - make sure your router firewall is working first of course. I agree with Dougal that this is the most likely problem area.
If you are not sure that each PC is able to "see" the other. This is the only "techie" bit of the process, and is not strictly necessary, but it does give you confidence that you don't have any faulty wiring in between. I would equally do this with a Mac or Linux PC in your situation. Basically, open a command prompt, and type: ipconfig - press enter and note the numbers that are displayed under "address", probably something like 192.168.0.2 etc. on one of the PCs and something similar on the other. Then on each PC type: ping w.x.y.z - where w.x.y.z is the address of the other PC. If everything is OK you'll get a message saying a reply was received. This proves that you have a valid connection. This process is identical on a Linux system by the way.
I must admit that I am not sure what limitations XP Home Edition puts in the way of all this, but I don't think it will be a problem. However if you have a proven connection then it should just be a matter of sharing the directories you want to share, and giving permissions to "everyone". You can then in theory just expand the "network" node in the Windows File Manager to see the shared areas on the other PC. As I say, it's a while since I have done this, but it is a standard and straightforward thing to do, and again quite similar to how it works on Linux.
I would not bother with the crossover cable, the router is the correct and easy way to link them. Like Macs, most PCs also have auto-sensing network connections - all manufacturers use the same or similar components these days.
Rest assured that this is basically a simple thing to do.
|
Barefoot Andrew
|
| orangepippin wrote: | | I would disable the firewalls on both PCs to start with - make sure your router firewall is working first of course. |
...or disconnect the modem/router from the phone line whilst you disable the firewall software on the PCs and have a fiddle.
A.
|
bagpuss
|
| Barefoot Andrew wrote: | | orangepippin wrote: | | I would disable the firewalls on both PCs to start with - make sure your router firewall is working first of course. |
...or disconnect the modem/router from the phone line whilst you disable the firewall software on the PCs and have a fiddle.
A. |
I will pint my OH towards this and see what he thinks
I think if the process involved disabling firewalls he will be switching off the cable modem for the process, better safe than sorry and all that
|
orangepippin
|
As BA suggests, all you need to do is disconnect the router from the phone line - absolutely right to play it safe, but leave the router on, just disconnected.
|
bagpuss
|
| orangepippin wrote: | | As BA suggests, all you need to do is disconnect the router from the phone line - absolutely right to play it safe, but leave the router on, just disconnected. |
we have cable I imagine the OH will just unplug the modem but leave everything else as it is
|
Barefoot Andrew
|
| orangepippin wrote: | | absolutely right to play it safe |
Indeed; my perimeter firewall reports a lot of unsolicited inbound traffic, on a variety of ports, every day. Much seeming to originate from academic institutions in Eastern Europe.
A.
|
MarkS
|
| orangepippin wrote: | | Rest assured that this is basically a simple thing to do. |
Which is why a quick google will find so many complicated work rounds and solutions .
|
