RV042 - restrict remote managent

Hi there,
is it possible to protect the remote management with a firewall rule if it is enabled?
I enabled the remote management with port 888, but i cannot restrict the access from external hosts.
Thanks a lot for every help.
Chris

Hi Christian, thank you for using our forum, I already answered your question in this link https://supportforums.cisco.com/thread/2246602.
I hope you find this answer useful,
Thank you!
Luis Arias.
Cisco Network Support Engineer.

Similar Messages

RV042 issue remote management access

Installed on two RV042 links with adsl load balance, everything works fine, except that an error occurs during a time I can access the remote management via Web RV042 both the LAN and the WAN, only after a while when accessing the page appears to login, but when you enter your username and password the browser is trying to give an error, the connection to the internet works normal again and I can only access the remote management to disconnect and reconnect the RV042, but updated the firmware the error continues, my RV042 is:
RV042 V03
Firmware v4.1.1.01-sp
I changed the default https port (443), to other ports but the error continues, someone had this problem?
André Szytko

hi there,
i can use google translate to try understanding your post. but i think its better for you to explain in english mate
regards,

RV042 - protect remote managent

Hi there,
is it possible to protect the remote management with a firewall rule if it is enabled? I changed the port to 888 and set a rule to deny all traffic to this port, but i can login to the router from external.
Thanks a lot for your help.
Chris

Hi Christian, thank you for using our forum, my name is Luis I am part of the Small business Support community. When remote management is enabled, you can use a web browser to access the configuration utility from anywhere on the Internet. In a web browser, enter http://:port, or enter https://:port if you have enabled the HTTPS feature. The highlight part is the important section that I want to clarify, If you want to restrict the access from WAN to your router you must disable the HTTPS feature in order to do that. Also if you disable the HTTPS feature, then users cannot connect by using QuickVPN.
Please go to Firewall > General and disable HTTPS option, then try to access your router remotely again.
I hope you find this answer useful
Greetings,
Luis Arias.
Cisco Network Support Engineer.

RV042 v3 Remote Management Port

I have a brand new RV042 v3 that I just updated to the latest firmware (v4.2.1.02) and have stumbled across an anomaly... I can only access the router from the WAN port using port 80. I happen to have it set to port 8080, but that doesn't work; I have to use standard port 80.
I have two other RV042 units running older firmware and they work as expected and follow the port that is filled in. This one has me puzzled and wondering if this is a bug in the firmware.

Yes, HTTPS is enabled, so the way to access the router is https://xxx.xxx.xxx.xxx, however, to make it less visible on the open internet, I want to use a less popular port, like port 8080.
I just tried my older routers and I guess they have the same bug, though I would've sworn they worked properly in the past. The too are accessible by either https://xxx.xxx.xxx.xxx or https://xxx.xxx.xxx.xxx:8080.
I would have thought by defining a Remote Access port that it would close all other ports, but I guess not.

Command line enable of VNC/Remote Management?

I have a situation where I need to enable remove mgmt (VNC) on my Mac at work, so I can get to it over VPN at home, to access my Parallels, etc. I can ssh to the system, but can't figure out how to enable the Remote Desktop (and it's specific parameters) via the command line. I believe it would be a defaults write.
Can someone point me in the right direction? I just want to restrict VNC with a Password, then disable it when I'm done.
Thanks.

Hi
Difficult to see why you're hesitating to use the kickstart utility as that will do what you originally asked. Just because it does not specifically mention VNC does not mean VNC is not running or working.
VNC Server and Client is built into OSX since 10.5. If you enable Remote Management it will open ports 5900 and 3283 on that workstation. Port 5900 is the VNC Port and port 3283 is the special control port Apple add to the built in VNC/ARD Agent to allow their dedicated management VNC Server application - Apple Remote Desktop - to offer a lot more than simple control for remote clients. You don't have to buy ARD to do what you want.
Enabling Screen Sharing only opens port 5900. On a Mac all you need is the local admin's name and password of the client workstation you're trying to control. If you're trying to control a mac from a PC then you'd need a dedicated VNC Viewer installing on the PC. Something like RealVNC Viewer. To allow the PC to control the mac you would have to add a VNC password option which should not be the same as the local admin's password.
Tony

Cant set Remote Management password

I am going nuts trying to find this out! When I right click the remote
management agent, the security selection is greyed out. I have full admin
rights to the tree. Does anyone know where this setting is to allow this?
thanks

I set this option but the security option on the systray icon is still
greyed out so I cant set the password. Any reason why this is restricted?
> On Wed, 09 Nov 2005 19:17:54 GMT, [email protected] wrote:
>
> > Does anyone know where this setting is to allow this?
>
> if the wks is imported you need to allow this in the remote management
> policies..
> --
>
>
> Marcus Breiden
>
> Please change -- to - to mail me.
> The content of this mail is my private and personal opinion.
> http://www.edu-magic.net

Effective Rights for Remote Management

How are an Administrator's Remote Management rights determined with regard to devices and users?
If an Administrator has Remote Control rights to a device, should they be able to remote control that device no matter what user is logged into it?
Conversely, if an Administrator has Remote Control rights to a user, should they be able to remote control that user no matter what device the user is logged into?
Thanks.

Michelsr,
it's the most restrictive combination that's effective - allowing
things like:
1) you have a device policy that says "allow", but the CEO logins in
and his policy is set to "deny", then you cannot remote control him
2) you have machines that contain sensitive information, so they have a
policy that says "deny", and a user logs in that has a policy that says
"allow", you cannot access that session.
Shaun Pond

Guide to remote manage Hyper-V servers and VM's in workgroups or standalone

This guide is based on the following 3 products:
Windows server 2012 (core)
Windows 8
Hyper-V server v3 / Hyper-V server 2012
The following guide will enable you to:
1: remotely manage your Hyper-V Virtual Machines with Hyper-V manager
2: remotely manage your Hyper-V servers' firewall with a MMC snap-in.
3: remotely manage your Hyper-V server (2012) with server manager
! This should also work for Core installations of server 2012, but I haven't tried.
This guide is purely focussed on servers in a WORKGROUP, or as a stand alone.
I CAN NOT tell you what you need to do to get it working in a domain.
* You can run these commands straight from the console (Physically at the machine) or through RDP.
* You will need to be logged on as an administrator.
* Commands are listed in somewhat random order; I do however advise to follow the steps as listed.
* Commands with ? in front of them are only ment to be helpfull for troubleshooting,
* and to identify settings and changes made.
* Commands and instructions with ! in front of them are mandatory.
- server: means the server core or hyper-v server (non gui)
- client: means the machine you want to use for remote administration.
- Some commands are spread over 2 lines; be sure to copy the full syntax.
> To enable the Hyper-V manager to connect to your server, you need to perform the following 2 actions: (Assuming you have already installed the feature)
1:
! Client: Locate the C:\Windows\System32\Drivers\etc\hosts file.
! right-click --> properties --> security
! click --> edit --> add --> YOURUSERNAME or Administrator --> OK
! then select this new user, and tick the "modify"-box under the "allow"-section.
! apply the change, and close.
! doubleclick the file, and open with notepad
! add the ip-address and name of your server (no // or other crap needed)
! Save the file
# I recommend putting a shortcut to this file on the desktop.
# If you change the ip-address of your server (e.g. move the server from staging to a live environment)
# you might forget to do so in the hosts file.
# Hyper-V manager, MMC, RSAT, and Server-manager all rely on the hosts-file to resolve the name.
# some of these might connect to their respective service on an i.p.-level, but some don't.
# This is the main reason you need to modify this file.
! USE AN ELEVATED CMD/POWERSHELL PROMPT TO CONTINUE !
# the next config needs to be done on windows 8.
# It seems that it's already preconfigured under server 2012
2:
! Client: dcomcnfg
! open component services --> computers
! right-click -> my computer -> properties
! select "COM SECURITY" tab
! under "ACCESS PERMISSIONS" select "edit limits"
! select "ANONYMOUS LOGON", and tick "remote access" under ALLOW
# Without this adjustment, you can't connect to your Hyper-V server
# with the Hyper-V manager if you're not in a domain.
> And if you haven't done so already... make sure you have enabled remote management number 4 on the Hyper-V server console.
> Next, is to get the MMC firewall snap-in working.
The reason for this, is to have a GUI available to configure it.
If you're happy without it, you may skip this and use a shell instead to do so.
? server: netsh advfirewall show currentprofile
# shows the current profile (public/domain/private) and its settings
# depending on your needs, you should set the right profile to fit your needs.
# You can easily do this when the MMC snap-in is done. (after you've followed these steps)
! server: netsh advfirewall set currentprofile settings remotemanagement enable
# enables remote management of the firewall on an application level
# (In other words: allows the firewall to be remotely managed)
! server: netsh advfirewall firewall set rule group="Windows Firewall Remote Management" new enable=yes
# allows remote management of the firewall, through the required firewall ports with TCP protocol.
# 4 rules will be updated to allow access: public & Domain, dynamic and endpoint-mapper.
# You can disable/add/change the rule from the MMC snap-in after finishing this guide.
# e.g. set the firewall through the MMC-GUI to only allow specific ip-addresses etc.
? server: netsh advfirewall firewall show rule all
# Shows a list of available rules, and their current state.
# when run from cmd, the list exceeds the maximum length for review.
# (from cmd,type:) start powershell, and run the command from there.
! Client: cmdkey /add:YOURSERVERNAME /user:USERNAMEONTHESERVER /pass:THEPASSWORDOFTHATUSER
# I recommend you to use a username with enough privileges for management
# All capital letters need to be replaced with your input
# CMD answers "credential added successfully" when you're done
! Client: locate MMC, and run it as an admin.
# In windows 8/2012, go to search and type MMC. Right-click the icon,
# and choose run as admin on the bar below.
! Client: application MMC: select "file" --> Add/remove snap-in
! --> (left pane) scroll down to "windows firewall" --> select and click "add"
! select "another computer"
! type the name of the server you want to manage (NO workgroup/ or //, just same name as you typed for cmdkey)
* Part 2 is done.
# Have a look by doubleclicking the firewall icon in the left pane.
# It looks and works the same as the GUI version that you are familiar with.
! Next is the Server Manager.
# Follow the steps listed to get your server listed and manageable in the server manager.
! Client: Open the created Firewall snap-in for your server.
! Find the 3 "Remote Event Log Management" entries in the list of INBOUND rules, and enable them.
! Open powershell --> in cmd windows, type: start powershell
! run the following line in powershell
! Client: in C:\Windows\system32> set-item WSMAN:\localhost\client\trustedhosts -value YOURSERVERNAME -concatenate
# WinRM Security Configuration.
# This command modifies the TrustedHosts list for the WinRM client. The computers in the TrustedHosts list might not be
# authenticated. The client might send credential information to these computers. Are you sure that you want to modify
# this list?
# [Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): y
# I recommend to choose yes; unless you like to pull some more hairs...
! server: winrm qc
# WinRM service is already running on this machine.
# WinRM is not set up to allow remote access to this machine for management.
# The following changes must be made:
# Configure LocalAccountTokenFilterPolicy to grant administrative rights remotely
# to local users.
# Make the changes? y / n
! select yes
! Client: open the server 2012 server manager
! click manage -> add server
! select the DNS tab, and type the name of your server
Done.
You can now manage your remote server through the familiar computer management GUI.
! Right-click your remote server, and select "Computer Management"
A few side notes:
? The Performance tab seems to list the local machine's performance, in stead of the remote servers'
? If you want Windows server backup, you need to right-click the server in the server manager, and select "add roles and features.
? it will then become available under the "computer management" of the remote server.
If you liked this guide you may thank my employer, Mr. Chris W.
for giving me the time to work it all out.
Cheers!

As a little update to the post, I'd like to add that replication, clustering and migration will not work in workgroup environments. Unless someone can provide an additional guide for this, I'd recommend anyone to no even bother to try.
To manage the standalone hyper-v server in a remote location over the internet, I would recommend the following:
Install windows 8 pro (x86 uses less resources!) as a vm on the host, and assign 2 network connections to it.
1 external (shared with host) (be sure you have a dedicated ip-address for it!)
1 internal connection.
What I did was this:
As soon as you've installed the win8 guest, proceed with the guide as described.
For the 1st step of the guide (hosts-file) use the ip-address you will later assign to the "internal" network switch of the host!
In my example, I'm using 10.0.0.1 for the host, and 10.0.0.2 for the guest.
To be clear: I first used the guide on a LAN-environment, and did all the steps from a "real" client to server on the LAN.
Then, installed the win8 guest on the host using the "real" clients' hyper-v manager over the LAN.
Next, assigned the 2 network connections to the VM, and configured them as follows:
external - as you would to be able to make your guest reach the internet.
internal - I used the following config:
ip-address: 10.0.0.2
subnet: 255.255.255.252
gateway - blank
dns - Blank
Now, when you get to the console of the hyper-v server (host) or RDP to it, go to network settings.
You'll see that the internal card has been added here as well.
Configure it as follows:
ip-address: static - 10.0.0.1
subnet: 255.255.255.252
gateway - blank
dns - blank
You should now be able to ping your guest (win8) on 10.0.0.2 if it's running.
Don't forget to enable ping response (option 4 on the host) to test connectivity the other way around as well (guest to host)
When you're done, you'll be able to RDP to the guest OS over the internet, and then connect to the host with server manager, hyper-v manager, and MMC.
Don't forget to enable each module on the hosts' firewall to make the snap-ins work!
Remote volume management requires your guest/client firewall INcoming ports to be enabled as well! not just the host.
Either update the firewall rules from the MMC gui as described in the guide, or use the following commands on the
hosts' powershell:
Enable the firewall rules with the command Enable-NetFirewallRule -DisplayGroup "USE_THE_COMMANDS_BELOW" (include the " " in the command)
Remote Service Management
Remote Volume Management
Remote Event Log Management
Remote Scheduled Tasks Management
Windows Firewall Remote Management
Windows Remote Management
You can get the list with Get-NetFirewallRule -DisplayName *management*
You can get the list with Get-NetFirewallRule -DisplayName *remote*
Commands provided with credits to F. verstegen
Cheers,
Michael.
Sigh...

How can i prevent users to delete remote management on their IPADs

hello everyone
i have Mac with OS X server i have created profile manager to manage the students I Pad's
students keep deleting the profile remote management profile
anyway to help me to manage their I PADS remotely

When configuring a profile in Profile Manager, if you edit the General entry you can set it to require a password before allowing a user to remove the profile. If you don't give users this password then they will not be able to remove it.

Screen sharing and remote management no longer working after some uptime

Server is withoiut monitor.
Users need to login via screen sharing from time to time.
"Enable screen sharing and remote management" is ticked in Server.app everything is working fine (for days, weeks).
ARD reports "Screen Sharing Available", so remote management is not running how it should.
Screen Sharing.app is "Connecting…" forever.
Kickstarting ARD (http://support.apple.com/kb/HT2370) does not help.
Restart fixes it.
Is there a workaround (over ssh) or a fix?

seduc wrote:
Do you know if
fdesetup authrestart
works then too?
Off-hand, no. I don't. See this posting, or as would be typical in any case, try it?

Screen Sharing and Remote Management

Is there a way in 10.6 to make both Screen Sharing and Remote Management run at the same time?
In the past (10.5), you could convince Mac OS to run both Screen Sharing and Remote Management to run simultaneously. I say "convince" because you could not enable them both through System Preferences. You could turn one on, then use Terminal to enable the other. This worked great for me, because I needed remote management for the machines I managed, and the users need screen sharing to work from home.
However, the work-around for 10.5 no longer seems to work for 10.6. Has any one gotten this to work yet for 10.6? Thanks!

I figured this out. First enable Remote Management via System Preferences. Then create /private/etc/ScreenSharing.launchd with 'enabled' as it's contents.

Mountain Lion Server: add network user to remote management

Hi,
So recently I have upgraded from Lion Server to ML Server. A little disappointing, but whatever, I've moved on and got everything almost back to where I had it with Lion.
My last few issues I believe are related but can't quite figure it out. In Lion I have an admin profile and then a network user profile that I used on my MBP bound with AD. I'm at the stage where my nre network user can log in on the server machine but I can't log in as the network user via screen sharing. I can't add a network user to Remote Management, and with Remote Management enabled Screen Sharing is greyed out. I'd really like this to work.
My second problem is that I can't bind my MBP to the server but even when bound the network user account can't log in.
Any body have any ideas?
Thanks!

I had this problem on a clean install.
The solution was incredibly simple for me, but only after I saw Ross.M's note about opening the Users & Groups settings panel (in the OS System Prefs, not in server) and rebinding to OD server under Login Options.
That was not the solution for me, but under Login Options I discovered a previously unnoticed pref for "Allow network users to login at login window." I had this option set (apparently by default) to "Only these network users:" but with an empty list. Adding my users to the list made it work perfectly.
Talk about KISS

Remote Management Config on NetInstall

Hello.
Is it possible to configure the Remote Management of a system when creating the Netinstall image? Say for example I install 100+ systems, I don't want to hook each one of these into a screen and manually configure Remote Management.
Any advice or pointers on things to read up on would be great.
Thanks.

Hello.
Is it possible to configure the Remote Management of a system when creating the Netinstall image? Say for example I install 100+ systems, I don't want to hook each one of these into a screen and manually configure Remote Management.
Any advice or pointers on things to read up on would be great.
Thanks.

System Image Utility - Create User - Activate Remote Management

When creating an image with system image utility, based on a DVD image instead of a cloned image, I cannot create a user and activate Remote Management.
I have created an installer package with Apple Remote Desktop that is supposed to do both, however it doesn't work. I do not get an error, but no user is created.
I have tried a post-install script however the dscl command is not recognized even if I put the path /usr/bin/dscl.
I even tried to use a popular package out there called "createUser" but that fails as well.
Has anyone had any luck with this when trying to make a moduler image with System Image Utility?
Message was edited by: NeedSomeAnswer

After configuring all the appropriate settings, I
push the "Create" button and it appears to start
working, prompts me for a location to save the actual
image itself, creates a folder with the default name
and then nothing happens.
ok here's the deal: i created a folder in my OSX server home directory labelled "images" and keep our multiple images there. although you CAN have your images on other drives or on the network, that would take a LOOOOOOOONG time to do the data transfer to the invisible netboot folder on your server. my advice: keep local copies of all images. save a ton of time for yourself, eh?
then, when it's time to use the system image suntility to load up an image, i go to that same location each time, call it up and have the app set to the prefs i want or need. i'm on 10.4.7 server and have had no problem using the software.
so try using images locally and then, if that doesn't work, upgrade to 10.4.7

Error while running Remote Manager for OIM11gR2

Hi,
I have 11gR2 Remote Manager configured in a Windows box on a different machine as OIM server. I am getting the below error while running the RM-
C:\RemoteManager\remote_manager>remotemanager.bat
C:\RemoteManager\remote_manager>set RM.ServiceName=RManager
C:\RemoteManager\remote_manager>set LIB_DIR=.\lib
C:\RemoteManager\remote_manager>set EXT_DIR=.\ext
C:\RemoteManager\remote_manager>set APPSERVER_TYPE=wls
C:\RemoteManager\remote_manager>set CLASSPATH=.;.\lib\xlAPI.jar;.\lib\xlVO.jar;.\lib\xlScheduler.jar;.\lib\xlRemoteManager.jar;.\lib\xerces.jar;.\lib\xlDataObjects.jar;.\lib\log4j-
1.2.8.jar;.\lib\xlUtils.jar;.\lib\xlLogger.jar;.\lib\xlCrypto.jar;.\lib\iam-platform-utils.jar;.\lib\oimclient.jar;.\ext\spring.jar;.\ext\commons-logging.jar;..\..\oracle_common\mo
dules\oracle.jrf_11.1.1\jrf-api.jar
C:\RemoteManager\remote_manager>"C:/Program Files/Java/jdk1.7.0/bin/java" -cp .;.\lib\xlAPI.jar;.\lib\xlVO.jar;.\lib\xlScheduler.jar;.\lib\xlRemoteManager.jar;.\lib\xerces.jar;.\li
b\xlDataObjects.jar;.\lib\log4j-1.2.8.jar;.\lib\xlUtils.jar;.\lib\xlLogger.jar;.\lib\xlCrypto.jar;.\lib\iam-platform-utils.jar;.\lib\oimclient.jar;.\ext\spring.jar;.\ext\commons-lo
gging.jar;..\..\oracle_common\modules\oracle.jrf_11.1.1\jrf-api.jar -Dlog4j.configuration=config\log.properties -DXL.HomeDir=C:\RemoteManager\remote_manager com.thortech.x
l.remotemanager.RemoteManager
Feb 9, 2013 2:00:54 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger info
INFO: Class/Method: RMIClientSocketFactory/static: sslEnabled : trueSSLContextAlgorithm : TLSKeyManagerFactory : @keymgrfactoryKeyStore : C:\RemoteManager\remote_manager\config\def
ault-keystore.jksKeyStoreType : JKSTrustStore : default-keystore.jks
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger info
INFO: Class/Method: RMISSLServerSocketFactory/createServerSocket Remote Manager server socket port is 12346
Exception in thread "main" java.lang.NullPointerException
at com.thortech.xl.remotemanager.RMISSLServerSocketFactory.createServerSocket(RMISSLServerSocketFactory.java:173)
at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:667)
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:317)
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:236)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147)
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:207)
at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:310)
at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:273)
at java.rmi.server.UnicastRemoteObject.<init>(UnicastRemoteObject.java:172)
at com.thortech.xl.remotemanager.RemoteManager.<init>(RemoteManager.java:80)
at com.thortech.xl.remotemanager.RemoteManager.main(RemoteManager.java:449)
C:\RemoteManager\remote_manager>
Any suggestions?

Hi,
I have 11gR2 Remote Manager configured in a Windows box on a different machine as OIM server. I am getting the below error while running the RM-
C:\RemoteManager\remote_manager>remotemanager.bat
C:\RemoteManager\remote_manager>set RM.ServiceName=RManager
C:\RemoteManager\remote_manager>set LIB_DIR=.\lib
C:\RemoteManager\remote_manager>set EXT_DIR=.\ext
C:\RemoteManager\remote_manager>set APPSERVER_TYPE=wls
C:\RemoteManager\remote_manager>set CLASSPATH=.;.\lib\xlAPI.jar;.\lib\xlVO.jar;.\lib\xlScheduler.jar;.\lib\xlRemoteManager.jar;.\lib\xerces.jar;.\lib\xlDataObjects.jar;.\lib\log4j-
1.2.8.jar;.\lib\xlUtils.jar;.\lib\xlLogger.jar;.\lib\xlCrypto.jar;.\lib\iam-platform-utils.jar;.\lib\oimclient.jar;.\ext\spring.jar;.\ext\commons-logging.jar;..\..\oracle_common\mo
dules\oracle.jrf_11.1.1\jrf-api.jar
C:\RemoteManager\remote_manager>"C:/Program Files/Java/jdk1.7.0/bin/java" -cp .;.\lib\xlAPI.jar;.\lib\xlVO.jar;.\lib\xlScheduler.jar;.\lib\xlRemoteManager.jar;.\lib\xerces.jar;.\li
b\xlDataObjects.jar;.\lib\log4j-1.2.8.jar;.\lib\xlUtils.jar;.\lib\xlLogger.jar;.\lib\xlCrypto.jar;.\lib\iam-platform-utils.jar;.\lib\oimclient.jar;.\ext\spring.jar;.\ext\commons-lo
gging.jar;..\..\oracle_common\modules\oracle.jrf_11.1.1\jrf-api.jar -Dlog4j.configuration=config\log.properties -DXL.HomeDir=C:\RemoteManager\remote_manager com.thortech.x
l.remotemanager.RemoteManager
Feb 9, 2013 2:00:54 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger error
SEVERE: Class/Method: ConfigurationClient/init encounter some problems: Unable to encrypt the value for: #text
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger info
INFO: Class/Method: RMIClientSocketFactory/static: sslEnabled : trueSSLContextAlgorithm : TLSKeyManagerFactory : @keymgrfactoryKeyStore : C:\RemoteManager\remote_manager\config\def
ault-keystore.jksKeyStoreType : JKSTrustStore : default-keystore.jks
Feb 9, 2013 2:00:55 AM com.thortech.util.logging.Logger info
INFO: Class/Method: RMISSLServerSocketFactory/createServerSocket Remote Manager server socket port is 12346
Exception in thread "main" java.lang.NullPointerException
at com.thortech.xl.remotemanager.RMISSLServerSocketFactory.createServerSocket(RMISSLServerSocketFactory.java:173)
at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:667)
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:317)
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:236)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147)
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:207)
at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:310)
at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:273)
at java.rmi.server.UnicastRemoteObject.<init>(UnicastRemoteObject.java:172)
at com.thortech.xl.remotemanager.RemoteManager.<init>(RemoteManager.java:80)
at com.thortech.xl.remotemanager.RemoteManager.main(RemoteManager.java:449)
C:\RemoteManager\remote_manager>
Any suggestions?

RV042 - restrict remote managent

Similar Messages

Maybe you are looking for