Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #102114 > unrolled thread

Sierra Upgrade File Sharing Problem

Back to article view | Back to comp.sys.mac.system

Contents

  Sierra Upgrade File Sharing Problem Nelson <nelson@nowhere.com> - 2017-03-09 13:52 -0500
    Re: Sierra Upgrade File Sharing Problem Alan Baker <alangbaker@telus.net> - 2017-03-09 12:18 -0800
    Re: Sierra Upgrade File Sharing Problem Lewis <g.kreme@gmail.com.dontsendmecopies> - 2017-03-09 22:38 +0000
    Re: Sierra Upgrade File Sharing Problem Jolly Roger <jollyroger@pobox.com> - 2017-03-10 15:14 +0000

#102114 — Sierra Upgrade File Sharing Problem

So I cloned my existing MacBook Pro running Snow Leopard to a new 
MacBook Pro and then upgraded the new macBook Pro to El Captain and 
thence to Sierra.  I made sure to give the new MacBook Pro a different 
network name and IP address.  But now when I try to connect back to the 
old MacBook Pro via file sharing, the new one connects to itself.  Took 
me a while to figure out it was connecting to itself since all the 
folders and file names are identical on both machines.

What could be causing this and how would one straighten it out?

-- 
Nelson

[toc] | [next] | [standalone]

#102116

On 2017-03-09 10:52 AM, Nelson wrote:
> So I cloned my existing MacBook Pro running Snow Leopard to a new
> MacBook Pro and then upgraded the new macBook Pro to El Captain and
> thence to Sierra.  I made sure to give the new MacBook Pro a different
> network name and IP address.  But now when I try to connect back to the
> old MacBook Pro via file sharing, the new one connects to itself.  Took
> me a while to figure out it was connecting to itself since all the
> folders and file names are identical on both machines.
>
> What could be causing this and how would one straighten it out?
>

Connect using the IP address...

[toc] | [prev] | [next] | [standalone]

#102130

In message <0001HW.D4E70EA2009F21C6B02919BF@news.astraweb.com> Nelson <nelson@nowhere.com> wrote:
> So I cloned my existing MacBook Pro running Snow Leopard to a new 
> MacBook Pro and then upgraded the new macBook Pro to El Captain and 
> thence to Sierra.  I made sure to give the new MacBook Pro a different 
> network name and IP address.  But now when I try to connect back to the 
> old MacBook Pro via file sharing, the new one connects to itself.  Took 
> me a while to figure out it was connecting to itself since all the 
> folders and file names are identical on both machines.

Considering the other posts you've made recently I feel very confident
in the following statement:

You fucked things up.

-- 
If lawyers are disbarred and clergymen defrocked, doesn't it follow that
electricians can be delighted, musicians denoted?

[toc] | [prev] | [next] | [standalone]

#102149

On 2017-03-09, Nelson <nelson@nowhere.com> wrote:
> So I cloned my existing MacBook Pro running Snow Leopard to a new 
> MacBook Pro and then upgraded the new macBook Pro to El Captain and 
> thence to Sierra.  I made sure to give the new MacBook Pro a different 
> network name and IP address.  But now when I try to connect back to the 
> old MacBook Pro via file sharing, the new one connects to itself.  Took 
> me a while to figure out it was connecting to itself since all the 
> folders and file names are identical on both machines.
>
> What could be causing this and how would one straighten it out?

I'd help, but I make a habit of avoiding helping people who sling
homophobic insults around about people they don't even know. Sorry, not
sorry.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [standalone]

Back to top | Article view | comp.sys.mac.system

csiph-web