Path: ...!weretis.net!feeder9.news.weretis.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: Marion <marion@facts.com>
Newsgroups: misc.phone.mobile.iphone
Subject: Re: For the adults - let's see if the Apple trolls apologize if they're wrong
Date: Fri, 18 Apr 2025 02:27:19 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <vtsda7$11h3$1@nnrp.usenet.blueworldhosting.com>
References: <vtr3qa$1gq7$1@nnrp.usenet.blueworldhosting.com> <vtr9j9$5lko$1@solani.org>
Injection-Date: Fri, 18 Apr 2025 02:27:19 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
	logging-data="34339"; mail-complaints-to="usenet@blueworldhosting.com"
User-Agent: Alan Baker insisted this line can not be changed
Cancel-Lock: sha1:AHQ3mBOMQ5tyxM0TNg7Xp/0ygg4= sha256:DeT5B3HPh5c34jcRWp5EOonv2HSrcWHlE2/vomG5+Gk=
	sha1:LWetm/+F7qPytDWYdznjOZAvmkU= sha256:oZeknTMtJ+mQ0R2gz+/Cv5bIOuZ0GdQjQvsJvy9icJw=
Bytes: 12798
Lines: 298

On Thu, 17 Apr 2025 16:17:45 -0000 (UTC), badgolferman wrote :


>> Currently there is a disagreement between me and the Apple trolls.

> I'm not sure if this is helpful or harmful�K.
> https://support.apple.com/en-us/103229

Thanks. I appreciate you looking. I posted that same link a while
ago but it doesn't really tell us explicitly what we want to know.

To test what we want to know, I just spent the energy making the 
connection from Windows and copying files and then debugging 
which port was used.

Even though I couldn't explicitly set the port to 445, my debugging 
results show unequivocally that Chris & Tyrone were right. I'm sure 
that Jolly Roger is also right but he never added any value. 

Chris did work. He added value. He deserves both thanks & an apology.
Likewise with Tyrone. He did work too. Hence he added value and hence he
also deserves a thank you and an apology.

I was wrong about iOS not allowing apps to bind to ports <1024.
My tests below prove that the LAN drive app (which has been on my 
iPad since I first tested it in 2019) did indeed bind to port 445.

Just like Chris said it did from the very beginning.
And just like Tyrone said it did from the very beginning.
Both of whom I believe tested it themselves before saying that.

Very clearly I am stating these two very clear unequivocal statements:
1. I apologize for not believing Chris & Tyrone & Jolly Roger.
2. Because what I said about the ports (even those I always said
   it was "as far as I know" or "as far as I understand it" or 
   "as far as I can tell", etc., simply happened to be wrong.

Period. 

FACT:
 *Apple iOS 16 apps apparently can bind to the privileged port 445.*
ASSESSMENT (of that fact):
 This makes bidirectional transfer FROM the PC command line easy!

Thanks everyone for answering the question of how it works with iOS.
See below for the gory details backing up my strong statements above.

 On Fri, 18 Apr 2025 00:34:58 -0000 (UTC), Marion wrote :

> I'll profusely and publicly thank you later as I still need to figure out
> what port it used, as this doesn't prove that it used ports below 1024.
> 
> But when I specify the port, that will tell us the answer.
> In the meantime, do you know why the iOS drives don't show up as mounted?

OK. I finished a few of the Amazon Vine free product reviews. 

I rebooted Windows and the iPad to start fresh.

1. On Windows, determine that nothing is mapped yet.
    net use 
2. On iOS, press "Not Now" to Apple's incessant nags
   to log into the Cupertino servers every second.
3. Keep Pressing more "Not Now" bags until Apple gets tired
   since it's a fact of life that's how Apple designed iOS
   that you *must* constantly log into Cupertino servers.
4. Open the "LAN drive" app on your iOS desktop
5. Note the (dynamic) identifying information you'll need for later
    Server \\myipad
    IP \\192.168.1.252
    SMB TCP 445
    NETBIOS UDP 137 138
5. Note the "Users" are "Anonymous" in "LAN drive" on iOS
6. Note the "Sharings" are "LANdrive" & "DCIM" on iOS
7. Press the green "START" button on the iOS "Lan drive" GUI
8. On Windows, type the connection command with the port specified
   net use Z: \\192.168.1.252:445\LANdrive
    System error 67 has occurred.
    The network name cannot be found.
9. Don't specify port 445 this time 
    net use Z: \\192.168.1.252\LANdrive 
     The command completed successfully.
10. Try it again on the other share.
     net use Y: \\192.168.1.252:445\DCIM 
     System error 67 has occurred.
     The network name cannot be found.    
11. Try it again without specifying the port.
    net use Y: \\192.168.1.252\DCIM 
    The command completed successfully.
12. Notice they're now both mapped, but not to port 445.
    C:\Windows\system32>net use
    New connections will not be remembered.
    Status       Local     Remote                    Network
   ----------------------------------------------------------------
   OK           Y:        \\192.168.1.252\DCIM      Microsoft Windows
Network
   OK           Z:        \\192.168.1.252\LANdrive  Microsoft Windows
Network
   The command completed successfully.

Hmm... just as I had figured would happen.
Now we have to figure out what port it's using.

I'm not gonna use Wireshark because I've been there, done that.
Too much data to filter (if you don't know what I mean, 
you've never used Wiresharp to capture pcap data).
[Filter=tcp.dstport == 445 or tcp.dst == 192.168.1.252]

I can use Resmon though.
a. Win+R > resmon
b. Tap the "Network" tab
c. Open "TCP Connections"
d. net use * /delete

e. This reports:
   Image = System
   PID = 4
   Local Address = 192.168.1.239
   Local Port = 31246
   Remote Address = 192.168.1.252
   Remote Port = 445 
   Packet Loss (%) = 0
   Latency (ms) = 105

Bingo!
This indicates that even though explicitly specifying port 445 in the 
net use command failed, the successful connection without specifying 
the port is indeed using port 445! Woo hoo! This is great news!

Let's check this with netstat:
a. Win+R > cmd > {ctrl+shft+enter}
b. netstat -ano | findstr "ESTABLISHED"
C:\Windows\system32>netstat -ano | findstr "ESTABLISHED"
   TCP    192.168.1.239:31246    192.168.1.252:445      ESTABLISHED     4
  This line shows an established TCP connection between 
  the PC (192.168.1.239 on local port 31246) 
  and the iOS server 192.168.1.252 on port 445. 
  The PID 4 is usually associated with the System process,
  which handles various low-level network functions like SMB.

Let's try PowerShell.
a. Win+R > cmd > {ctrl+shft+enter}
b. C:\Windows\system32> powershell
c. Test-NetConnection -ComputerName 192.168.1.252 -Port 445
d. The results (after a bit of a wait) are...
    ComputerName     : 192.168.1.252
    RemoteAddress    : 192.168.1.252
    RemotePort       : 445
    InterfaceAlias   : Wi-Fi
    SourceAddress    : 192.168.1.239
    TcpTestSucceeded : True

Hmm.. so why didn't specifying the port work?
C:\Windows\system32>net use Y: \\192.168.1.252\DCIM
The command completed successfully.

C:\Windows\system32>net use Y: /delete
Y: was deleted successfully.

C:\Windows\system32>net use Y: \\192.168.1.252:139\DCIM
System error 67 has occurred.
The network name cannot be found.

C:\Windows\system32>net use Y: \\192.168.1.252\DCIM
The command completed successfully.

Anyway, even though I can't get the Windows 10 "net use"
command to specify the port explicitly, I'm satisfied
(and quite surprised!) that the debugging tools showed
that, indeed Chris, Tyrone & even Jolly Roger were 
quite correct that iOS is allowing the LAN drive 
freeware to bind to ports below 1024, specifically 445.

There is no doubt of that conclusion in my mind at this
point since I tested it and explicitly ran debuggers.

I publicly and humbly apologize to Chris, Tyrone, and 
to Jolly Roger for not believing them up until I tested it
myself and found that I was wrong and they were right.

I have no problem saying I'm wrong because I learned
that iOS is uniquely different from Android in that
iOS does apparently allow 3rd-party apps to bind to 
========== REMAINDER OF ARTICLE TRUNCATED ==========