Re: Cable for transfer of data?

Terry Pinnell <terrypin@xxxxxxxxxxxxxx> wrote:

"jameshanley39@xxxxxxxxxxx" <jameshanley39@xxxxxxxxxxx> wrote:

On 12 Mar, 21:13, "GB" <NOTsome...@xxxxxxxxxxxxx> wrote:
<jameshanle...@xxxxxxxxxxx> wrote in message

news:d960b979-684e-45fc-8812-8daf3b7373a3@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Windows file sharing can be a bit of a nuisance to configure. From
memory, last time I did it, it requires many conditions to be
satisfied.. like Creation of user accounts with same name on each
computer. May still be worth looking into though. For its smoothness
once set up.

I think that you are vastly exaggerating the difficulty of doing this. You
certainly don't need to have the same user name on the new machine. It's
actually very easy.

<snip>

As one of the other posts on this thread says, use the network setup wizard.
XP pro automatically defaults to simple file sharing if connecting to a win
xp home workgroup. It all works swimmingly.  The only possible problem the
OP may have is when the wizard asks for the workgroup name. iirc the default
workgroup for xp home is 'XPHOME'. I am not sure what the default is for xp
pro, but the OP might need to type XPHOME into the box.


I tested the "Network Setup Wizard" just for the hell of it.

Of course, a wizard is not really something a techie would use. I am
suprised you mentioned it / your use of it / your experiences with it.

I don`t know about all that you mentioned..
I don`t know what an XP HOME workgroup is (one computer on XP HOME?
All of them?). I have not used XP HOME much. If you are just
thinking about the name.. Then regarding that name you mentioned. I
can tell you that in XP PRO , the wizard suggests the name MSHOME as a
workgroup name. (so maybe you meant MSHOME not XPHOME ?).

I know that in Win XP HOME, the only option available for file
sharing, is simple file sharing. Is that what you meant when you said
the wizard "defaults to that". I wouldn`t say it defaults to that.
It is all that is available on XP HOME..

If you choose SFS prior to running the wizard.. Then the "network
setup wizard" sets things for that if they are not set already.
Enables the Guest account if and adjusts the "Local security policy"
such that Guest is not denied.
If you do not choose SFS prior to running the wizard. Then the wizard
will not make those amendments.

I don`t use wizards though.. Most techies don`t. For obvious reasons.

<snip>

Many thanks for taking the trouble. I'm Keeping much of this thread
for practical use/implementation when the PC arrives in a couple of
weeks. (Minor setback due to Visa 'declining' MESH's transaction, just
as they did with the balance on our summer holiday a week earlier.
Seems standard security procedure now, probably for all amounts over
£1K. PITA, but probably inevitable ...)

To focus any future further discussion (I can't get too *much*
advice!), my OS will be XP Pro (presumably SP2), and as already
established the current one is XP Home (SP1).

Although networking unfortunately remains a black art to me, I did
briefly flirt with one a few years ago, for transferring a little data
with the Win98 PC in my shed/workshop (used primarily for practical
electronics, a consuming hobby at the time). But the data transfer was
at best iffy. Signal strength issues. And also I sometimes lost the
network entirely and had to fiddle around with sw re-establishing it.
W98 was apparently 'SP1' too, with some downside. I can't precisely
recall this network's status when I gave up on it, and it roughly
coincided with the decline in my shed activity anyway. But, coming
back to the current context, I wonder if there are any *remnants* of
that setup which might hinder my work in a couple of weeks? Or some
password I should retain? Or remove?

I probably will use the wizard if, as it seems from the various posts,
it's as reliable as it sounds. Providing there's a fall-back of
abandoning it if it goes pear-shaped, without permanent damage!

I have a '10m Ethernet Network Cable' ('UTP Patch Cord, Cat 5e,
suitable for connecting a PC to a network switch or router') due to
arrive tomorrow from Amazon, and I might be tempted to try it out on
another PC I have in this office. It's the predecessor of my wife's
new PC, XP Home, sitting here for the last 6 months. Before I turf it
out to provide space for the new one (probably to the shed, with a
ripple effect that will probably end up with a visit to the skip for
some ancient chunk of hardware!) Could I safely try some of these
suggestions on it?

Got the cable but disappointed to see that I can't experiment with it
on the old XP PC I mentioned above, as it has no appropriate socket.

--
Terry, East Grinstead, UK
.

Relevant Pages

  • Re: sharing files on windowns xp pro and xp home 111111111111
    ... wizard and set up a workgroup i gave him my workgroup name but when we both ... either so do you think is because he is runing xp home edition and im runing ... What connection option did you specify to the Network Setup Wizard? ...
    (microsoft.public.windowsxp.network_web)
  • Getting my new PC networked with the old?
    ... GB recommended I use Add New Network Wizard. ... I already have an internet connection, via the router, using the cable ... The default entry for Workgroup is MSHOME, ...
    (uk.comp.homebuilt)
  • Re: The SBS 2003 Network Configuration Wizard InOp
    ... I then tried the Network Configuration Wizard again, ... Wizard, I click "OK" to install the wizard, then I get the same old error " ... PCNS Support Team ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot see computer...
    ... I just needed to run the Network Setup Wizard. ... WinXPsp2) are fine and can see shared folders and swap files. ... in the workgroup and vice versa. ...
    (microsoft.public.windowsxp.network_web)
  • Re: The SBS 2003 Network Configuration Wizard InOp
    ... Wizard was not installed. ... Click Connect to the network now to try again and click Yes ... If the wizard fails to install, ... MS however support introduction of SBS into an existing AD. ie. a situation ...
    (microsoft.public.windows.server.sbs)