|
controller cannot see minimServer
|
|
21-08-2012, 19:39
Post: #24
|
|||
|
|||
RE: controller cannot see minimServer
(21-08-2012 03:00)psme Wrote: Yes I checked there is a java 1900 port bounding on my PC 192.168.1.120 IP. Please see attached screen cap. Since that 192.168.1.120:1900 bounding is grouped with Kinsky, I thought it's used by a client/controller program and didn't think it is minimServer. Btw, why all other UPnP servers are under 0.0.0.0:1900 but minimServer uses 192.168.1.120:1900? Is it the way of java? In the latest screen cap, I see other servers under 192.168.1.120, which seems to be different from what you are saying here. As I requested in my previous post, please can you redirect the complete output from netstat -nab to a file (in both the working and failing cases) and attach both files here. It's important to provide the complete output, not just a few entries in a screen cap. The ohNet developers have responded to my problem report and they've asked me for some more information about the problem. Please can you answer all the following questions about the devices that are showing this problem (your PC and your QNAP):
Quote:So I closed minimServer, and start it again. But this time minimServer gave a Red icon with this error: This means you are trying to use 64-bit MinimServer with 32-bit Java. You have two options: a) Uninstall 32-bit Java from the PC and install 64-bit Java if you don't already have it installed. Leave 64-bit MinimServer installed. b) Uninstall 64-bit Java from the PC and leave 32-bit Java installed. Uninstall 64-bit MinimServer and install 32-bit MinimServer instead. This will prevent any possibility of getting a 32/64 mismatch between your Java installation and your MinimServer installation. |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)

Search
Member List
Calendar
Help



