NCF and Netware Remote Manager

Hi there.
Is there any issues with Novell client Firewall and Netware Remote
Manager inside my LAN?
When I try to access NRM on ports 8008/8009, for some servers I can
connect but for others I can't.
If I unload NCF, everything comes back to normal with NRM.
I have already created rules to allow these ports, but nothing.
Any ideas?

Brad Averbeck wrote:
> Are the servers on the same subnet as you? Do you have that subnet
> trusted? This is my situation and maybe that's why I don't have a
> problem with it. You could try trusting the server IP. You get
> there by clicking on the options button/system tab/settings button
> for Lan settings. Click on add and type in the IP address.
>
> Brad
>
>
> Carlos Almeida Jr. wrote:
> > Brad Averbeck wrote:
> >
> >
> > > I use NRM all the time and have had no problems. When you look at
> > > the activity, does it show a block for ports 8008/8009 and a
> > > reason?
> > >
> > > Brad
> > >
> > > Carlos Almeida Jr. wrote:
> > >
> > > > Hi there.
> > > >
> > > > Is there any issues with Novell client Firewall and Netware
> > > > Remote Manager inside my LAN?
> > > >
> > > > When I try to access NRM on ports 8008/8009, for some servers I
> > > > can connect but for others I can't.
> > > >
> > > > If I unload NCF, everything comes back to normal with NRM.
> > > >
> > > > I have already created rules to allow these ports, but nothing.
> > > >
> > > > Any ideas?
> >
> >
> > Brad,
> >
> > There is no block at all, at least I can't find any.
> >
> > I've looked at Firewall Log Viewer and there is nothing blocked. As
> > I said, I can connect to some servers, not to some of them.
> >
> > I have created a rule for ports 8008/8009 but it didn't work too.
Yes, the servers are on the same subnet.
I have the subnet trusted and I have added the IP of the server
especifically as trusted, and it is not working yet.

Similar Messages

Nagios, certs, and NRM/ Remote Manager

We just created a brand new xen guest OES11sp2/SLES11sp3 server, and already the certs for the NRM are no good, they're still using the ones created in YAST during the SLES install portion.
(eDirectory certs were created and all four validate just fine)
For now, I just made an exception in my browser, but when I go to the NRM and go to check Health status, I get a nagios login window. that's new.. and if I try to log in with my eDir credentials, it fails, and now I just see a 500 error. The rest of NRM works okay though.
If I export the eDir certs and use keytool to export them to server.pem and server.key and overwrite the ones at
/etc/opt/novell/httpstkd (well, actually, /etc/ssl/servercerts) will that fix nagios or is there another issue here?
And I'm wondering why the eDirectory certs didn't overwrite the YAST certs.. we always have the install do that.

This gets weirder.
I used "openssl x509 -in servercert.pem -text" on the new server to check the servercert.pem cert under /etc/ssl/servercerts, and it turns out it IS the eDirectory cert.
I've restarted both nagios and httpstkd, but the httpstkd configure page claims it's using the old Yast cert; it is configured to use the /etc/ssl/servercerts (through a softlink).
Firefox accepts the cert fine, Chrome complains that the certificate doesn't match the URL, which is ridiculous. It's absolutely the same.
I hate certs.
Anyway, in either case, I still get the 500 error with nagios. It asks for a login, I have no idea what it wants. My edir user doesn't work, and neither does root.

Vista, IE7 and Virtual Office (VO) or Remote Manager

A Windows Vista laptop (Vista Business Edition) is trying to browse to the Virtual Office web page published by their Novell SBS 6.5 server using IE7. Nothing appears in the browser. If I look at the source for the page, there is a bit of code showing, referencing a Java script. I get the same result when I try to use the Netware Remote Manager web page at http://servername:8008 or https://servername:8009. It is the same if I use the server's IP address instead of a resolvable name. The browser windows says "Connecting" and the status line shows "Waiting for 10.170.170.5"
I loaded up Firefox, and after allowing a Certificate Exception, I am able to browse to the server's Virtual Office page from the same computer.
I have installed the Certificate from the server into the Trusted Publishers container, I have set both the http://servername and https://servername into the trusted sites list.
What else do I need to do in Vista to get the web page to work?

The answer is to turn off TLS 1.0 in the Advanced Internet Options
page.
Warren
On Wed, 06 May 2009 01:56:01 GMT, WFRUSH
<[email protected]> wrote:
>
>A Windows Vista laptop (Vista Business Edition) is trying to browse to
>the Virtual Office web page published by their Novell SBS 6.5 server
>using IE7. Nothing appears in the browser. If I look at the source for
>the page, there is a bit of code showing, referencing a Java script. I
>get the same result when I try to use the Netware Remote Manager web
>page at http://servername:8008 or https://servername:8009. It is the
>same if I use the server's IP address instead of a resolvable name. The
>browser windows says "Connecting" and the status line shows "Waiting for
>10.170.170.5"
>
>I loaded up Firefox, and after allowing a Certificate Exception, I am
>able to browse to the server's Virtual Office page from the same
>computer.
>
>I have installed the Certificate from the server into the Trusted
>Publishers container, I have set both the http://servername and
>https://servername into the trusted sites list.
>
>What else do I need to do in Vista to get the web page to work?

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

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

[Kindly help me understand]Urgent:Provisioning using Remote Manager

Hi,
I have a requirement to auto provision a resource to a 3rd party system as soon as it is created. We can not do it using DB Connector, as well as WebServices.
The remanining option is to have their jar in our system and invoke a Java Task, which introduces tight coupling and not well suited.
So, I have thought about creating a Remote Task, where in I would introduce my jar, which will just open a URL Connection to the 3rd party system using Remote Manager.
My query here is:
1. Is this a feasible and a good approach?
2. If yes, then how do i connect to this api using Remote Manager. I created a Remote Task, and defined a IT Resource Type definition. As per my understanding, we need to introduce a IT Resource of type Remote Manager as well. However, the design console is now showing any type of IT Resource Form.
OIM version used: 11.1.1.5 and references used : http://itnaf.org/2011/07/27/installing-and-testing-remote-manager-on-oim-10g/
Please suggest how to go about it.
Thanks!

Kewl

Rd230 simple question re remote management module

Hi,
Just purchased and installed rd230. Installed win2008 R2 SP1 (manually...not with easystartup).
I'm reading the user guide for remote management module. Looks great! One thing...how do I setup the RMM???(IP address...etc). It's not in the BIOS setup...I don't see any prompt at boot to enter a config utility for it....any help??
Thanks
M
Solved!
Go to Solution.

You will find conrfiguration information and answers to other RMM related questions in
ThinkServer RD230 and RD240 Remote Management User GuideThinkServer RD230 and RD240 Remote Management User Guide:
download.lenovo.com/ibmdl/pub/pc/pccbbs/thinkservers/00697mst.pdf

E4200V2 Remote Management is inoperative

Remote Management does not work on this router. Version of firmware is reported to be current (no update available). The user guide says click on administration and then Management, find Remote Management and Select remote management and select enabled... However in the "Linksys Smart WiFi" interface there is selection for management and remote management.. Firmware is 2.1.39.!
It is a real problem when a router can not be managed remotely!!!

Rudi F wrote:
Remote Management does not work on this router. Version of firmware is reported to be current (no update available). The user guide says click on administration and then Management, find Remote Management and Select remote management and select enabled... However in the "Linksys Smart WiFi" interface there is selection for management and remote management.. Firmware is 2.1.39.!
It is a real problem when a router can not be managed remotely!!!
Rudi F wrote:
Correction to my post = However in the "Linksys Smart WiFi" interface under Administration there is NO selection for
management and remote management..
Linksys routers with Smart Wi-Fi Interface can be accessed remotely through www.linksyssmartwifi.com once you have signed-up for a Smart Wi-Fi account using your email address. This actually make things easy for us since we don’t need to set-up remote management anymore in order to remote access our routers.

Capture error code returned by VB script from the OIM Remote Manager

Hi All,
I am trying to provision to Exchange using powershell and OIM remote Manager.
RM is installed in the Exchange server and a VB script is called by the RM to perform the necessary provisioning operations.
Certain error codes are configured in VB script according to the script execution.
How can I get the return codes back to the RM and then to OIM adpater, so that I can publish appropriate error messages by writing them in the Adapter responses.
Below is my current code, but it does not capture return codes.
Can the variable 'i' get the return codes fron the VB script?
if (fScriptFile.exists())
String sCmd = scriptPath + " " + sUPN;
log.debug("Firing Powershell command:" + sCmd);
Process localProcess = localRuntime.exec("cscript.exe " + sCmd);
log.debug("Script Executed ");
int i = localProcess.waitFor();
localProcess.getOutputStream().close();
log.debug("Process Exit Value " + i);
sResult = i == 0 ? "EXCHANGE.REMOTE_SCRIPT_RUN_FAILURE" : "EXCHANGE.REMOTE_SCRIPT_RUN_SUCCESS";
Please help..
Thanks and Regards.

Your VB script must be calling a powershell script.Check if powershell script returns any error message to your vbscript.I

Schema entry for Remote Management Policy

Does anybody know the schema entry for Remote Management Policy in a user
object? Specifically the entry that says "Use These Settings and Ignore
Remote Management Policy"?
Thanks!
Mike

On Wed, 20 Apr 2005 18:57:10 GMT, [email protected] wrote:
> Does anybody know the schema entry for Remote Management Policy in a user
> object? Specifically the entry that says "Use These Settings and Ignore
> Remote Management Policy"?
console one could tell you..
Marcus Breiden
Please change -- to - to mail me.
The content of this mail is my private and personal opinion.
http://www.edu-magic.net

Remote Management lists server IP

Hello,
I have a NW6 server running Zen 4.0.1 and when I right-click on a user
object and click "Remote Management" it lists there IP and the IP of the zen
server. This only happens on some machines, most work fine.
We are a mixed IP/IPX environment.
Any ideas or reasons this may happen???
Scott Windmiller
University of Maryland
Department of Psychiatry
Information Systems

On Tue, 02 Nov 2004 14:59:52 GMT, Scott Windmiller wrote:
> I have a NW6 server running Zen 4.0.1 and when I right-click on a user
> object and click "Remote Management" it lists there IP and the IP of the zen
> server. This only happens on some machines, most work fine
hmm the zenserver ip could show up because the user is using the
middletier..
Marcus Breiden
Please change -- to - to mail me.
The content of this mail is my private and personal opinion.
http://www.edu-magic.net

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...

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.

Difference between remote management and vnc

Difference between remote management and vnc

By VNC I will presume you mean 'Screen Sharing'.
Screen Sharing in System Preferences - Sharing is purely for remote control and is based on the VNC protocol with a few extra features added by Apple.
Remote Management in System Preferences does everything Screen Sharing does and is fully compatible with another Mac doing just Screen Sharing, i.e. it allows remote control. However it can also do additional things. It is intended for use with Apple's Remote Desktop Administration software which can use this to send files to a Mac, send (Unix) commands to a Mac and ask for a report from the Mac (e.g. how much RAM it has).
If you don't have Apple Remote Desktop there is no real point enabling Remote Management instead of Screen Sharing.
Both Screen Sharing and Remote Management can also be configured to allow 100% standard VNC connectivity from say a PC, as standard they only accept connections from Macs.

NCF and Netware Remote Manager

Similar Messages

Maybe you are looking for