+- MinimServer Forum (https://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: Support (/forumdisplay.php?fid=4)
+--- Thread: subnet not found after setting ohnet.subnet (/showthread.php?tid=4193)
Pages: 1 2
subnet not found after setting ohnet.subnet - bogkor35 - 15-10-2017 23:09
When I set to 192.168.1.0 (for IP address = 192.168.1.66 with subnet mask = 255.255.255.0) I receive during minim server startup "subnet 192.168.1.0 not found". IP address is a static IP address. Any idea?
When ohnet.subnet is empty then minim works fine, server communicates also with minim watch which is on the same network (IP=192.169.1.107 with subnet mask = 255.255.255.0).
RE: subnet not found after setting ohnet.subnet - simoncn - 16-10-2017 09:42
It sounds like your local subnet is 192.169.1.0, not 192.168.1.0.
RE: subnet not found after setting ohnet.subnet - bogkor35 - 17-10-2017 10:48
It was a mistake - minim watch address is 192.168.1.107 with subnet mask = 255.255.255.0. I think minim watch address doesn't matter because minim watch may be down when minim server starts.
RE: subnet not found after setting ohnet.subnet - simoncn - 17-10-2017 15:28
What machine (computer or NAS) are you using to run MinimServer? What network adapters does this machine have? Are you using a VPN or anything similar that could change the network address available to MinimServer? Are you sure you have typed the subnet correctly in the ohnet.subnet field?
RE: subnet not found after setting ohnet.subnet - bogkor35 - 17-10-2017 23:27
I'm using minim server on Windows Server 2016. Network adapter is Ethernet (USB). IP address is defined static. No VPN or similar at all. The subnet was typed correctly. Here you find output from ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : WIN-2T77DRRN8L5
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : ASIX AX88179 USB 3.0 to Gigabit Ethernet Adapter
Physical Address. . . . . . . . . : 00-13-3B-9B-5A-8B
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.66(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 52.178.167.109
NetBIOS over Tcpip. . . . . . . . : Enabled
RE: subnet not found after setting ohnet.subnet - simoncn - 18-10-2017 09:32
Thanks for this information. Please do the following:
1) Start MinimServer without the ohnet.subnet setting
2) From the minim icon, select 'Show log'
3) In the log window, set the logging level to Debug
4) In the System tab of the Properties window, set ohnet.subnet to 192.168.1.0 and click OK
5) From the minim icon, select Restart
6) When you get the red icon with "subnet 192.168.1.0 not found", zip the minimserver.log file and attach the ziipped file to a post here. This log file is in the folder C:\users\your-user-name\AppData\Roaming\MinimServer\data.
7) In the log window, set the logging level back to Info
I will look at the log file and let you know what is causing the problem.
RE: subnet not found after setting ohnet.subnet - bogkor35 - 23-10-2017 12:38
Hi,
When I change dynamically subnet to '192.168.1.0' from '' then it works after restarting server from minim watch (and sounds better). I'm attaching zipped log file. But the described problem happens when I restart my computer after - then minim communicates that this is wrong subnet and I have to change to '' again.
RE: subnet not found after setting ohnet.subnet - simoncn - 23-10-2017 14:24
This log shows the subnet being found and everything working correctly.
Perhaps the subnet is not available when MinimServer starts. Could you try delaying MinimServer startup by a short time to check this?
RE: subnet not found after setting ohnet.subnet - bogkor35 - 23-10-2017 19:42
I'm attaching log file from minim server during PC restart when subnet is not found. Restarting from minim watch doesn't help - minim server is still red light.
Suprising for me is that if I follow below procedure from minim server then server starts:
- go to properties and change subnet to ''
- restart and minim starts properly with subnet = ''
- go to properties and change subnet to '192.168.1.0'
- restart and minim starts properly with subnet = '192.168.1.0'
RE: subnet not found after setting ohnet.subnet - simoncn - 24-10-2017 09:32
Thanks for this information and the log.
The subnet is not found when MinimServer starts during PC startup because MinimServer is being started before your network connection is available. I will make a change to MinimServer to enable you to solve this problem by setting the MinimServer delayStart property. At present, this delay happens after the subnet check and I will change this so that the delay happens before the subnet check.
I will also fix the other problem that you reported with the subnet not being found on a MinimServer restart unless the ohnet.subnet property was modified before the restart.
Both these changes will be available in the next MinimServer update. This update should be available soon.