| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 43 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 101:32:41 |
| Calls: | 290 |
| Files: | 905 |
| Messages: | 76,534 |
On 7/23/24 12:39 PM, Hugh Hood wrote:
Here's the 'wall' that I'm up against -- It appears that Windows 10
*Home* doesn't have a built-in SMB 3 server, only a built-in SMB 3 client. >>
It does offer the deprecated SMB 1 server option, but the SMB FST won't
work with that.
So, any and all suggestions are hereby solicited, short of upgrading to
Windows 10 *Pro*. I tolerate Windows out of necessity -- I'm not a fan.
Am I missing something obvious?
Windows 10 Home does include SMB 2/3 server functionality. I've tested
it with the SMB FST, and it works. I think you may just be seeing that
there is an option to _disable_ SMB 1 support, but not SMB 2/3.
There are some Windows settings that can have the effect of blocking SMB connections, such as setting the network to "Public" or certain firewall settings. If you have another modern computer available to act as a
client, I'd suggest testing with that to confirm that the SMB server is working and accepting connections. If that works but you still can't
connect from the GS, let me know.
Before I throw in the towel on getting Stephen's cool new SMB FST
working for my specific use case, may I ask someone who is currently
running David Schmidt's GSPort .v31 (with Marinetti / Uthernet LL 1.0.5)
on a Windows 10 Home computer to see if they can access their SMB2
shares that are on the *SAME* computer? (ie - local shares)?
Stephen was certainly correct -- Windows 10 Home does have an SMB2
server. I have it enabled and running, in fact, and have spent an embarrassing amount of time in the Windows registry (and elsewhere) and viewing Wireshark logs trying different things suggested on the Windows
help forums to make a connection.
Regardless, all I can manage is: "An SMB connection could not be
established with the server."
This is normal due to how winpcap/npcap's packet injection works. It
is also a limitation of VMs using bridged networking on a machine.
You would need a router that does "hairpin routing" since your
emulated machine and host machine can't directly see each other's
packets.
On 8/4/2024 2:08 PM, Hugh Hood wrote:
Before I throw in the towel on getting Stephen's cool new SMB FST
working for my specific use case, may I ask someone who is
currently running David Schmidt's GSPort .v31 (with Marinetti /
Uthernet LL 1.0.5) on a Windows 10 Home computer to see if they can
access their SMB2 shares that are on the *SAME* computer? (ie -
local shares)?
Stephen was certainly correct -- Windows 10 Home does have an SMB2
server. I have it enabled and running, in fact, and have spent an
embarrassing amount of time in the Windows registry (and elsewhere)
and viewing Wireshark logs trying different things suggested on the
Windows help forums to make a connection.
Regardless, all I can manage is: "An SMB connection could not be
established with the server."
Chris,
Thanks for that explanation.
One question -- if a router offers a 'port forwarding' feature, would
that suffice for the hairpin routing you mention?
Thanks for the networking education. It's definitely one of my weak areas.
Hugh Hood
Yes, there are known issues with the MacIP link layer, which likely
cause the problems you're seeing. (Basically, it does Memory Manager
calls in an interrupt handler, when it may not be safe to do so.) Maybe
the issues will be fixed someday, but for now an Ethernet card is a
better bet for stable TCP/IP networking on the GS.
Yes, Netatalk 2.x and Samba have incompatible metadata representations. Netatalk 3.x is more compatible with Samba, but drops AppleTalk support.
(It can be used with AFPBridge, though.)
This is normal due to how winpcap/npcap's packet injection works. It is
also a limitation of VMs using bridged networking on a machine. You
would need a router that does "hairpin routing" since your emulated
machine and host machine can't directly see each other's packets.
One question -- if a router offers a 'port forwarding' feature, would that suffice for the hairpin routing you mention?Port forwarding is used with external access to your router, allowing you to point incoming connections to specific NAS drives, webcams, or computers on your LAN.
Hugh,> One question -- if a router offers a 'port forwarding' feature, would that suffice for the hairpin routing you mention?Port forwarding is used with external access to your router, allowing you to point incoming connections to specific NAS drives,webcams, or computers on your LAN.Good routers will let you change an incoming port number, and redirect it to a different port number on a specific device. This would allow you for instance to have multiple NAS drives on your LAN, with each one