| Re: Some excerpts from SMB FST Read Me file [message #421990] |
Sun, 04 August 2024 14:08  |
Hugh Hood
Messages: 692
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
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."
FWIW, other TCP apps work on the emulated GSPort computer, including Ewen's Webber and SAFE2.
So, I'm just asking if perhaps it has something to do with GSPort under Windows 10 Home accessing SMB shares on the local computer.
If someone has that specific instance working, I trudge on until it works. Otherwise, I'll stop beating my head against the wall.
{Also, I don't have a modern computer to access the Windows shares via SMB2, as my old Tiger PowerMac uses SMB1}.
Thanks.
Hugh Hood
On 7/24/2024 1:51 PM, Stephen Heumann wrote:
> 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.
>
|
|
|
|
| Re: Some excerpts from SMB FST Read Me file [message #421991 is a reply to message #421990] |
Sun, 04 August 2024 22:40  |
Christopher G. Mason
Messages: 160
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
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."
>
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.
|
|
|
|
| Re: Some excerpts from SMB FST Read Me file [message #422007 is a reply to message #421991] |
Mon, 05 August 2024 11:38 |
Hugh Hood
Messages: 692
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
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
On 8/4/24 9:40 PM, Christopher G. Mason wrote:
>
> 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."
>>
|
|
|
|
| Re: Some excerpts from SMB FST Read Me file [message #422008 is a reply to message #422007] |
Mon, 05 August 2024 17:42 |
Christopher G. Mason
Messages: 160
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
On 8/5/2024 11:38 AM, Hugh Hood wrote:
> 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
>
Port forwarding will not provided this. Unfortunately "hairpin" routing
isn't a common feature in a typical consumer router.
|
|
|
|
| Re: Some excerpts from SMB FST Read Me file [message #422010 is a reply to message #421991] |
Mon, 05 August 2024 19:45 |
Oliver Schmidt
Messages: 137
Registered: January 2013
Karma: 0
|
Senior Member |
|
|
Hi,
> 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.
At least at some point in the past it helped to install the Microsoft
Loopback Adapter and make the traffic go to / come from there. Because that
approach makes the traffic accessible by npcap.
Regards,
Oliver
|
|
|
|
| Re: Some excerpts from SMB FST Read Me file [message #422011 is a reply to message #422007] |
Tue, 06 August 2024 03:14 |
someone
Messages: 53
Registered: March 2012
Karma: 0
|
Member |
|
|
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 responding to FTP Port 21, but then to access them individually from outside by using unique port numbers in the FTP client.
Cheers - Ewen
|
|
|
|
| Re: Some excerpts from SMB FST Read Me file [message #425282 is a reply to message #422011] |
Thu, 21 November 2024 01:35 |
barana
Messages: 95
Registered: March 2013
Karma: 0
|
Member |
|
|
Speccie <someone@somewhere.com> Wrote in message:r
> 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 responding to FTP Port 21, but then to access them individually from outside by using unique port numbers in the FTP client.Cheers - Ewen
I never understood this, thx!
--
~Die then Soar~
----Android NewsGroup Reader----
https://piaohong.s3-us-west-2.amazonaws.com/usenet/index.htm l
|
|
|
|
Members
Search
Help
Register
Login
Home
