XPost: misc.phone.mobile.iphone

On 2025-04-17 07:34, Marion wrote:

On Thu, 17 Apr 2025 13:45:59 +0000, Tyrone wrote :

I'm digging for the answer - like an intelligent person should.

No. An intelligent person would accept the facts. A petulant child would
remain in denial.

Please remember those words when you decide whether to apologize or not
when you're forced (by facts) to admit iOS/Android can't bind to port 445.

Make note of these two very important data points:
\\192.168.1.24:445 (on iOS is using the iOS SMB client)

Chris explained that was incorrect.

C:\> net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

Yes, and if you were bright enough, you'd realize that that command
proves your interpretation of the first line was wrong.

Bonjour/mDNS can make things simpler but it won't change the underlying interaction other than to allow automatic discovery of the hostname (e.g., \\my-iphone.local) and the port (which will still be 445 in this test).
C:\> net use Z: \\192.168.1.24\SharedFiles /user:tyrone mypasswd
C:\> net use Z: \\my-iphone.local\SharedFiles /user:tyrone mypasswd

Yet I'm well aware of how Apple users think, which is that only Apple can >>> (magically) do the impossible. It's a defining feature of all Apple users. >>

Why is this impossible? Do you think it is hard coded into Unix forever that >> no one can ever use port 445? Do you think Apple can't change anything they >> want? In their own source code?

<your deflection snipped>

In this case, you Apple trolls still can't figure out the difference
between what an iOS SMB server does versus what the iOS SMB client does.
\\192.168.1.24:445 (on iOS is using the iOS SMB client)
C:\> net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

Saying it a second time doesn't make you any more correct.

Another defining feature of all Apple users is they have no idea how
anything works. That's also what makes Apple users what they are.

I know exactly how this works. I have been networking computers since before >> you were born. The only troll here is you, claiming it can't work because YOU
say it can't work. Circular logic much?

Heh heh heh... first off, I never said I was a networking expert. In fact, I've said many times that I'm NOT a networking expert.

Yet, just as Alan Baker claims to be an expert in things he knows nothing about, you don't appear to know the difference between a server & a client.
\\192.168.1.24:445 (on iOS is using the iOS SMB client)

I've never claimed to be an expert in anything, Arlen.

I've claimed that I own a BMW 135i...

...which you claimed I couldn't possibly own because I didn't know which
of "bimmer" or "beemer" applies to BMW cars versus their bikes (still
don't know, nor care).

I've claimed that I race a 1998 Van Diemen RF98 Honda Formula F, and
that I'm now a race driving instructor with the Sports Car Club of
British Columbia...

...which you claim cannot be true because you're stuck on the idée fixe
that the shape of the arc made by a racing car in a corner is a catenary
(it's not, and I can prove it).

To use the iOS SMB server, you need to run a command like this:
C:\> net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

No, that is the command to connect TO an SMB server, nitwit.

You even admitted that Windows SMB needs port 445. The app SHOWS it is using >> port 445.

Heh heh heh... as an SMB client.
\\192.168.1.24:445 (on iOS is using the iOS SMB client)
C:\> net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

Third time is as wrong as the first two.

Therefore, it IS using port 445.

You need to go back to Costco where you bought that "Networking Expert"
name plate and return it since you can't figure out the difference between what an iOS SMB client does, versus what an iOS SMB server does.
\\192.168.1.24:445 (on iOS is using the iOS SMB client)
C:\> net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

Fourth time: still wrong.

Don't worry. Costco will refund your money... no questions asked.

AGAIN, why don't you DL the app "LAN Drive SMB Server" and try it? BTW this >> app has existed for a least 6 years. So this is not a new solution.

Copying a file from iOS to a Windows share is using the iOS SMB client.

No one is denying that.

"LAN drive SAMBA Server Client" from Webrox is an SMB SERVER (and
client) app for macOS, and it allows you to connect to an iOS device
FROM a Windows client.

Copying a file from a Windows share to iOS is using the iOS SMB client.

Same rebuttal.

Do you even have any idea how to test using an iOS SMB server with Windows?
\\192.168.1.24:445 (on iOS is using the iOS SMB client)
C:\> net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

Fifth time in, you're still a nitwit.

Why are you always claiming something is "impossible" that you yourself have >> never tried? Remember, you ALSO said it was "impossible to copy a photo from
Windows to iOS without using internet servers".

Heh heh heh,... I expressly said I don't doubt that SMB clients can copy a file from Windows to iOS and vice versa. The issue was *initiating* it.

No. That was your first goalpost shift.

Do you STILL cling to that absurd claim? As we proved, it not only CAN be
done, but it is easy to do using built-in functionality in both Windows and >> iOS.

First, tell me which device you are sitting at when you initiate that copy.

Using "LAN drive SAMBA Server Client", the Windows machine.

Of course, after proving that claim to be wrong, you moved the goal posts by >> stating "No, I meant that I want to do all file moves FROM Windows. But that >> is impossible".

I operate my entire Android interactions over Windows, not on the phone itself. That's well known. Why would that have to be crippled on iOS?

And here we are, proving that it IS possible by using an SMB Server app on >> iOS. And yet you are still claiming it is "impossible", only because you say >> it is "impossible".

heh heh heh... I wonder if you'll apologize as vehemently as you attack
when you finally realize you mixed up what a server does versus a client.
\\192.168.1.24:445 (on iOS is using the iOS SMB client)
C:\> net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

Sixth time, and you're still dumb as a stump.

Note that Bonjour or mDNS can make the discovery hidden so expressly state the port so that we're sure of exactly which port is being used please.

Now, you are AGAIN changing the "issue" into "What port can this app be using?
It CAN'T be port 445 because I say so".

A non-rooted/jailbroken iOS/Android device can't bind to port 445 (AFAIK). You can pick any reason you like.

False.

Don't blame me for your inability to like what happens to be how it works.

Which is just more deflection away from you being wrong twice about moving >> files between Windows and iOS. But keep on digging that hole. In a couple more
days you will have been proven wrong 3 times.

heh heh heh... Let's see how many (if any) of you Apple trolls will
publicly apologize for not understanding an SMB server versus the client.
\\192.168.1.24:445 (on iOS is using the iOS SMB client)
C:\> net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

Seven times, and you're dumber than dirt.

What will your next deflection be? "What I REALLY want is to pretend it is >> 2005 and do all of this over a USB cable"?

Simply copying a file from iOS to Windows and back is NOT exercising an SMB server even though you "think" that's what it's doing. It's not.

When you use the second command below, you are connect a Window system
to an SMB server, idiot.

\\192.168.1.24:445 (on iOS is using the iOS SMB client)
C:\> net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

Seven times, and you're dumber than dirt.

Since you bought a "Networking Expert" placard from Costco, let's test it
out by having you run the simple "net use" command with your iOS server.

C:\> net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd
If you are correct, then that command should report it succeeded. Right?
Show us a screenshot of: "The command completed successfully."
You would then be able to access the files and folders within
\\192.168.1.24\SharedFiles through File Explorer or by using the
assigned drive letter.

If I'm correct, then I predict you'll get a Connection Timeout or Refusal with some kind of typical Windows networking error message such as

a. "No network provider accepted the given network path."
b. "The network path was not found."
c. "The remote computer refused the network connection."
d. A timeout error might also occur as Windows waits for a response

In summary, when you run the "net use" command above, specifying the port
you claim is being bound by iOS, it will either work - or it won't work.

While that is correct, you're an idiot for stating the utterly obvious.

You tell me since you insist it works.
(I already assume it will fail based on my understanding of how iOS works.)

Prove me wrong if you're so sure non-jailbroken iOS binds to port 445.

Let's do it!

First, me launching and configuring "LAN drive SAMBA Server Client" on
my iPhone 16:

<https://drive.google.com/file/d/1Wd_XBpwaMan3ApHGVF7eQT88GMsA7FaS/view?usp=share_link>

Note the IP address AND hostname (which isn't "localhost" because I
changed it)

Next, on my Windows 10 machine across my living room accessed via
"Windows App" (formerly "Windows Remote Desktop"; a much more accurately descriptive name; typical Microsoft), I first browse the available
devices in Network:

<https://drive.google.com/file/d/1Wm5MN3jOwyWSPjKz1PrVPWKBp9XT0f2p/view?usp=share_link>


And then after opening "iPhone16", I see:

<https://drive.google.com/file/d/1MS3PgV68Rl8YllgzE4qtWmr-rqJYX_Np/view?usp=share_link>

Golly, gee!

Who could have imagined that Arlen would have it all wrong...

...again...

...aside from EVERYONE...

...(except BGM of course)?

:-)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)