Computers by name

[mesa57]

I have the following (simple) test setup

PC1 - Softether server with secure nat enabled (no local bridge)
DHCP enabled, gateway and dns filled, virtual nat : N/A
OS : windows XP (pro)
PC2 - Client connect to server on PC1 (windows XP)
PC3 - Client connect to server on PC2 (windows 7)

What I am trying to achief is a little mesh network with 3 pc's
Now PC3 is able to ping PC2 via its name (e.g. ping PC2)
Also PC2 is able to ping PC3 (e.g. ping PC3)
But neither PC2 or PC2 is able to ping PC1 by its name (ping PC1)
Pinging to IP address works, but not via its (netbios) name

No difference if I enable/disable virtual nat on the server.
The ping to PC1 always tries to reach it's physical adapter IP address instead of the secure nat IP address, that's why the ping to PC1 fails.

Is there any solution, so that a ping to PC1 will go to it's secure nat's address ?

[kh_tsang]

Method one: Change the server to Linux OS and Linux version supports tap device. You can add a tap device so that a network adapter will appear and connect to the client. Remember to give a static IP to the adapter and leave the default gateway empty.

Method two: Install a client as well and connect to itself and set a static IP with default gateway empty.

[mesa57]

For an adhoc network a linux server would not be a solution I think.
In an adhoc network any pc should be able to take over the server role.

So I installed a client as well, observing that when connecting to itself the gateway is not used.
But that leads to the problem that there is no route from PC1 to PC2 or 3.
So PC1 cannot ping PC2 or PC3.

[kh_tsang]

Then wait for the answer from the developer is more appropriate.

[mesa57]

Hopefully the source will be available soon, so I can look into the problem myself ;)

[inten]

mesa57 hi.
I've been reading an explanation of your problem for several times today and only now realized what you want to achieve. My question to clarify is do you want PC2 and PC3 could ping PC1 (softether server) name that resolves by its NAT IP address via broadcast ARP request?

[mesa57]

An arp request would be to establish the mac <-> ip relation. This works fine, all machines can ping each other by ip address.
To ping each other by name however, a nbtns request should deliver the netbios name.
This works from PC2 to PC3 and vise versa, but not to the softether server PC1.

Goal is to build an mesh/ad-hoc network INCLUDING the server PC.
Software like hamachi / comodo unite is able to do this in a very simple way.
Softether however seems to be more gateway or server oriented.
Ideal would be if none of the PC's has a server role.

[inten]

and please post the output of the command below here, like:

C:\>vpncmd /server localhost /password:PASS_HERE /hub:US-16 /cmd:dhcpget

Item |Value
-------------------------------+--------------
Use Virtual DHCP Function |Yes
Start Distribution Address Band|192.168.0.10
End Distribution Address Band |192.168.3.250
Subnet Mask |255.255.252.0
Lease Limit (Seconds) |7200
Default Gateway Address |192.168.3.254
DNS Server Address 1 |192.168.3.252
DNS Server Address 2 |192.168.3.253
Domain Name |
Save NAT and DHCP Operation Log|Yes
The command completed successfully.

[mesa57]

Ok :

pncmd command - SoftEther VPN Command Line Management Utility
SoftEther VPN Command Line Management Utility (vpncmd command)
Version 2.00 Build 9387 (English)
Compiled 2013/09/16 12:45:42 by yagi at pc25
Copyright (c) SoftEther Project. All Rights Reserved.

Connection was established with VPN Server "localhost" (port 992).

You have administrator privileges for Virtual Hub 'vital3' on the VPN Server.

VPN Server/vital3>dhcpget
DhcpGet command - Get Virtual DHCP Server Function Setting of SecureNAT Function
Item |Value
-------------------------------+--------------
Use Virtual DHCP Function |Yes
Start Distribution Address Band|192.168.31.10
End Distribution Address Band |192.168.31.200
Subnet Mask |255.255.255.0
Lease Limit (Seconds) |7200
Default Gateway Address |192.168.31.1
DNS Server Address 1 |192.168.31.1
DNS Server Address 2 |None
Domain Name |vital.nl
Save NAT and DHCP Operation Log|Yes
The command completed successfully.

[inten]

192.168.31.1 - is it your real/working DNS server?

[inten]

skype me, it would be faster to discuss ksimonenko outlook com
I have a solution for you, it is a bit tricky but works just fine to us.

[mesa57]

inten wrote:
> 192.168.31.1 - is it your real/working DNS server?
No, in the network there is no dns server except for the ISP one.
This is specified in the securenat configuration.
Sorry that I cannot skype you, I am on my work now.

[inten]

Deploy DNS and point it to the DHCP/NAT settings.

[inten]

or you can use HOSTS file.

[mesa57]

Of course a host file on each client works.
As well as adding a route statement for the client/server IP addresses (netbios name service returns the IP assigned to the physical network interface).
But that would require additional configuration at the clients (as well as the server).
Deploying dns probably probably will work, however how would the dns server get the IP address form the securenat ?
I am afraid that there is no simple solution and that softether is not the optimal solution for setting up an ad-hoc/mesh network.

[inten]

Frankly I do not understand your concerns, all that I have said works at our installation (without any changes done on the clients). And Yes, Softhether requires many changes to serve better but even now it is enough to build a rather big VPN network ;-)

[inten]

Hope this helps.

[inten]

More to say, we have ~20 virtual hubs with local networks (you call it mesh network) where clients work.

[mesa57]

Ok solved :)
By installing and running the client on the server (PC1) I was able to ping the server by it's name (PC1).
However pinging from PC1 to PC2 did not work ...
ipconfig /flusdns and nbstat -R did not help ...
But I saw a domain suffix was added which came from the router (dd-wrt router).
Then I deleted a previous lease entry in the router for PC2.
After that pinging to PC2 also worked and resolved to its softether address.

Thank you for thinking with me, an specially for the tip of running the client on the server PC1. This was the solution, but something else was in the way.

[inten]

We did not install SE client on the server. I believe this will work work without the SE client installed.