ZEN7 on OES Linux

hi there,
i installed zfs7 on oes linux and i cant connect to the mms database (
consoleone / management site status ) .
Any help would be nice.
Regards
Wolfgang Hackl

Hi Ron ,
i installed the pds an mms service on oes .. the documentation says nothing
about site services only run on netware or windows ....
Wolfgang
>>> Ron van Herk<[email protected]> schrieb am 16.04.2006 um 23:10 in
Nachricht <bpy0g.730$[email protected]>:
> What component did you install???
> The site server isn't supported on OES Linux.
>
> Ron
>
> "W Hackl" <[email protected]> wrote in message
> news:[email protected]..
>> hi there,
>>
>> i installed zfs7 on oes linux and i cant connect to the mms database (
>> consoleone / management site status ) .
>> Any help would be nice.
>>
>> Regards
>>
>> Wolfgang Hackl

Similar Messages

OES Linux, Print Solutions

Hello all,
I am currently using Netware 6.5 SP5(OES Netware SP2), and wandering what
print solutions are available for the OES Linux platform. Specifically, is
NPDS available on OES Linux? If so is it the primary solution or is there
a different solution?
A direction to documentation would be more helpful. Any assistance is
appreciated.
Regards,
Matt Rigor

Matt,
NDPS isn't really state of the art on NW6.5.
iPrint is, as well on Netware as on OES Linux. Check the manuals.
Uwe
Novell Support Connection Volunteer SysOp
Please don't send me support related e-mail unless I ask you to do so.

OES Linux DHCP Management Quesiton

Previously, under Netware, I could use the DNS/DHCP console to match ip to machine hostname; however, I'm noticing that I do not have this ability under OES Linux's DHCP management utility. I looked in the leases file on the linux server but to my dismay it only displays the mac address.
What are my options?

Originally Posted by gwcisco
Previously, under Netware, I could use the DNS/DHCP console to match ip to machine hostname; however, I'm noticing that I do not have this ability under OES Linux's DHCP management utility. I looked in the leases file on the linux server but to my dismay it only displays the mac address.
What are my options?
Your only option (as far as I am aware--and if I understand you correctly) is to go with OES 2 SP 3, follow TID 7006450, and that is about it. The information is coming from the leases file itself. Unfortunately, you can't get 100% of what you were used to on NetWare on OES. Many things have been ported over, but some things have not.

PXE on OES Linux SP2

Trying to get PXE to respond to a client on OES Linux SP2.
Novell-pxydhcp, novell-tftp, and novell-zmgprebootpolicy are all
running. UDP ports 67, 69, 111, 4011, and 18753 are listed in
FW_SERVICES_EXT_UDP (and INT_UDP). Firewall has been restarted.
Workstation does not get PXE connection. Previously, this machine did
get a connection to a Netware server running PXE.
Any thoughts on what we're missing?
Thanks.
Lyle

On Tue, 12 Jun 2007 18:07:06 GMT, [email protected] wrote:
> DHCP is on a Netware server on same network segment.
did you configure option 60 on this dhcp server? if yes remove it
Marcus Breiden
If you are asked to email me information please change -- to - in my e-mail
address.
The content of this mail is my private and personal opinion.
http://www.edu-magic.net

Moving a NetWare iPrint installation to an OES/Linux cluster

Hi folks,
I have an iPrint installation on my NetWare 6.5 cluster that i want to
move to my OES/Linux cluster. The two clusters are completely
independent at present, and need to remain that way. Is there any way i
can move printers and drivers without recreating them and manually
duplicating the settings?
Thanks,
Paul
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFE0AExafGwptjWFZkRAnT9AKCjmXKk7dwuIXA3QlYPRM mywN0u1ACeOrZX
NdOTqsZ/wbpjUD8iq744i1I=
=szY+
-----END PGP SIGNATURE-----

Niclas Ekstedt wrote:
> On Wed, 02 Aug 2006 01:34:43 +0000, Paul Gear wrote:
>
> The Consolidation Utiltity available from the Download site
> is capable of moving PA's between Managers.
Thanks, Niclas - i'll check it out.
Paul
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFE0T/rafGwptjWFZkRApzVAKCpmDhCGzGM5s3MKnaIyYo+47kmqwCfd xfz
8lnocVoQ+peLvI60muL19a0=
=+/p6
-----END PGP SIGNATURE-----

Windows XP and OES Linux

We are running a NetWare 5.1, 6.0, 6.5, OES 6.5 and now OES Linux shop. I
have just built and installed the OES Linux server into a new tree until I
can figure it out. Our workstations are all Windows 2000 and XP SP2 with
Novell Client 32 4.91.
Being that I'm new to Linux, how do our users connect to the server? If you
could point me to a tid, that would be great!
Thanks.

Newbie wrote:
> Ok, I must be missing something. The only window that pops up is the
> Microsoft login window with ID and PWD options... Should the Novell 4.91
> client pop up instead?
>
>
> "Jeremy" <Jmeldrum@nospam_novell.com> wrote in message
> news:KEacf.2740$u%[email protected]...
>> Newbie wrote:
>>
>>> Thanks, linuxjoe.
>>>
>>> I have figured out how to setup the "Samba" and when I use Windows
>>> Explorer
>>> and browse to the "Microsoft Network" I can see the server and shares.
>>> I click on the share and I can't login.
>>>
>>> I went into iManger and configured a Workstation and User (admin) for
>>> accessing Linux.
>>> The server info:
>>> Tree: Linux_Tree
>>> Server: OES_Linux
>>> Context: test (both admin and server are in here)
>>>
>>> What do I put in the Login Box that pops up on my Windows XP machine?
>>>
>>>
>>>
>>>
>>> "linuxjoe" <[email protected]> wrote in message
>>> news:Xi6cf.2329$u%[email protected]...
>>>> Newbie wrote:
>>>>
>>>>> Being that I'm new to Linux, how do our users connect to the server?
>>>>> If
>>>>> you could point me to a tid, that would be great!
>>>>
>>>> You should be able to connect to it with a client over ncp as well. But
>>>> you
>>>> can also do it over ftp, http, nfs, etc.
>>>>
>> When the login box pops up, you use the same information you normally do,
>> tree, context, and server. The difference would be that you can now put
>> the oes linux server name (or IP address) in the the sever field. You
>> can also map to the SYS volume just as you would a NetWare server.
I am confused with your comments. If you have a user running Windows XP
with the 4.91 windows client, he will have a login popup. The Login window
will ask for the username and password. If you hit the advanced button, it
will show you the tree, context, and server fields. Currently you will
have your tree, context and server from your previous login populated. If
you want to log into the OES Linux server, you can change the server field
to point to the OES Linux server's IP or server name. There is nothing
different when accessing the NSS volumes on a OES Linux from a windows
workstation.

OES Linux- SLP not registering

Installed 1st OES2-SP1 server in tree, and configured SLP as part of
the installation. The server initially registered and was visible
when browsing the network, but since the installation this server
cannot be seen. The slp.log file reports the following:
Mon Feb 2 15:34:52 2009
SLPD daemon started
Command line = /usr/sbin/slpd
Using configuration file = /etc/slp.conf
Using registration file = /etc/slp.reg
Using SPI file = /etc/slp.spi
Listening on loopback...
Listening on 192.168.10.198 ...
Multicast socket on 192.168.10.198 ready
SLPv1 Service Location General Multicast socket on 192.168.10.198
ready
Unicast socket on 192.168.10.198 ready
Broadcast socket for 255.255.255.255 ready
Agent Interfaces = 192.168.10.198
Agent URL = service:service-agent://192.168.10.198
Startup complete entering main run loop ...
WARNING: Reconnect tries to agent at 192.168.10.172 exceeded maximum.
It is possible that the agent is malicious. Check it out!
..172 is the DA for the tree and is functioning well with all the NW
boxes. I'm still struggling to get comfortable with Linux, what have
I missed??
thanks,
DG

This is the NetWare-Communications forum, you'd want one of the OES forums.

OES linux "rights" command, [Public] user and Windows woes

Hey all,
I've been trying to figure out a solution for this, and although I thought I figured it out, it ends up I can't seem to figure it out. Hear me out.
We run an automated ZCM imaging system, and part of that is the ability to have any user authenticate on successful image using the Novell client. Once this is done, the first login should start installing a series of bundles/applications.
As MS Office 2010 is a rather large install, I keep the files/folders stored on a NSS volume, aptly named:
//oesserver/media/nss/APPS/MICROSOFT/MS Office 2010 SP2 - Admin Install
I would like ALL users to have access to this directory but since we run on a weird container layout, and our licensing permits for a rather large number of installs, I wanted to give the [Public] user read+filescan rights to each server's /media/nss/APPS/MICROSOFT/MS Office 2010 SP2/ directory, so regardless of where you are mapping with any user, that user would then have access to said folder.
If I use either the iManager plugin or directly using the Novell client method of applying [Public] as a trustee, it works, and the client can see the folder.
I have over 30 servers that each have the identical path, so in my sleuthing I found the OES command to perform: rights
So I performed the following command:
rights -f "/media/nss/APPS/MICROSOFT/MS Office 2010 SP2 - Admin Install" -r rf trustee [Public]
If I then show the results, there are successful:
rights show
The problem, however, is that within Windows, from any login, when I right-click the folder and check the trustees, I do not see that user in the list, and in return, that user has no access to the directory.
If I then run my command to remove the rights from the OES server:
rights -f /media/nss/APPS/MICROSOFT/MS\ Office\ 2010\ SP2\ -\ Admin\ Install/ -r none delete [Public]
And then run a "rights show" again, the Public user is removed correctly.
What I can't seem to figure out is why the command will allow me to set trustee rights to [Public], that "rights show" will validate that the rights are currently assigned, but from a Windows perspective I have no access to that directory.
I have done a "rights show" on the drive when assigning the rights from the Novell client and/or iManager, and there is NO difference in how "rights show" see the [Public] user listed.
Has anyone else ever seen this?
If I specify a user in my tree, it works correctly on both ends.
rights -f "/media/nss/APPS/MICROSOFT/MS Office 2010 SP2 - Admin Install" -r rf trustee username.ou.o.tree_name
rights show will then show me the appropriate trustee, and the user can see the path in Windows.
This restriction seems limited to the [Public] user, but I have no idea how to do this properly.
I'd like to avoid doing it by hand, because I want the ability to script all my changes and remotely and efficiently.
Any advice?
Thanks!

On 16/06/2014 18:34, Uwe Buckesfeld wrote:
> I recall a problem with the rights command on Linux, not sure if it has been fixed. Is your server fully patched?
Are you thinking of TID 7014932? That's an issue with OES11 SP2 which is
fixed by installing the April 2014 OES11SP2 Hot Patch for NCL.
HTH.
[1] https://www.novell.com/support/kb/doc.php?id=7014932
Simon
Novell Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

DHCP - Cannot add text option for VOIP phones in OES Linux

While working through this, I solved the issue, but decided to post this anyway as it may help others to find these sorts of errors.
I'm working on migrating from NetWare 6.5sp8 to OES11sp2. Client has Shoretel VOIP phones. Existing NetWare-based DHCP has no problem. Option 156 has been configured to give out the required text information that Shoretel phones require.
Problem is that I could not get the OES11 DHCP to run with that option. Nor could I migrate the existing option over - the Migration Tool (in OES11) says it successfully migrates DHCP, but I cannot start the dhcpd daemon. Error is that it failed, and in the rc.dhcpd.log file I see an error:
LDAP Line 26: unknown option dhcp.Shoretel_Boot.
LDAP Line 26: unexpected end of file
LDAP: cannot parse dhcpService entry 'cn=newdhcpservice,o=LIBRARY'
Configuration file errors encountered -- exiting
If I look in the file (created when LDAP reads DHCP config from eDirectory apparently) dhcp-ldap-startup.log I can see the problem entry at line 26:
option Shoretel_Boot "FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,L AYER default-lease-time 259200 ;
This option does NOT show up in the newdhcpservice option when I look at it in ConsoleOne, or DSBROWSE, or DNS/DHCP Management Console.
This option DOES show up in the DNS/DHCPManagement Console if I look at the DHCP (NetWare) tab and look at Other DHCP Options for some of the configured subnets, but it actually has different text from the above, specifically:
FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,LAYER2 TAGGING=1,VLANID=9
Note that it does not have a " character anywhere in the entry. This option is configured as a Global DHCP text option.
Novell TID 7009464 mentions the issue, though not for Option 156. In that TID there is this:
"Situation #2
Migrate a working DHCP server with DHCP options that are of type "Text" to an OES server.
Load the DHCP server service... it fails to load and gives similar errors to the ones listed above."
Under resolution the TID says to delete and recreate the dhcp service object without the text option and it will load. That doesn't work for me as I still get an LDAP error pointing to the Shoretel_Boot unknown option. (I dare not try deleting it from the NetWare DHCP config and risk breaking the client's phone system).
One of the options in the TID to fix this is to re-enter the data using the DNS/DHCP Management Console - but that didn't work.
Here is the answer:
First, the log files are misleading. The error message points to not being able to read the newdhcpservice object entry - but the problem was elsewhere. In fact the problem showed up in the logs even when there were no option 156 entries at all in any object inside the newdhcpservice or the newdhcpservice object itself. The problem existed in the NetWare configuration of the object for one of the dhcp subnets.
Specifically, there was an illegal character in the text entry for option 156 - the # character was in there, like this:
FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,LAYER# 2TAGGING=1,VLANID=9
If you look at the error log entry for syntax error you can see that the option 156 text stopped at the # symbol, and then default-lease-time was appended to the end.
Removing the # symbol got things working.
Craig Johnson
(former Novell partner / sysop)

On 30/08/2014 21:16, phxazcraig wrote:
> While working through this, I solved the issue, but decided to post this
> anyway as it may help others to find these sorts of errors.
>
> I'm working on migrating from NetWare 6.5sp8 to OES11sp2. Client has
> Shoretel VOIP phones. Existing NetWare-based DHCP has no problem.
> Option 156 has been configured to give out the required text information
> that Shoretel phones require.
>
> Problem is that I could not get the OES11 DHCP to run with that option.
> Nor could I migrate the existing option over - the Migration Tool (in
> OES11) says it successfully migrates DHCP, but I cannot start the dhcpd
> daemon. Error is that it failed, and in the rc.dhcpd.log file I see
> an error:
>
> LDAP Line 26: unknown option dhcp.Shoretel_Boot.
> LDAP Line 26: unexpected end of file
> LDAP: cannot parse dhcpService entry 'cn=newdhcpservice,o=LIBRARY'
> Configuration file errors encountered -- exiting
>
>
> If I look in the file (created when LDAP reads DHCP config from
> eDirectory apparently) dhcp-ldap-startup.log I can see the problem entry
> at line 26:
>
> option Shoretel_Boot
> "FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,L AYER default-lease-time
> 259200 ;
>
>
> This option does NOT show up in the newdhcpservice option when I look at
> it in ConsoleOne, or DSBROWSE, or DNS/DHCP Management Console.
>
> This option DOES show up in the DNS/DHCPManagement Console if I look at
> the DHCP (NetWare) tab and look at Other DHCP Options for some of the
> configured subnets, but it actually has different text from the above,
> specifically:
>
> FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,LAYER2 TAGGING=1,VLANID=9
>
> Note that it does not have a " character anywhere in the entry. This
> option is configured as a Global DHCP text option.
>
> Novell TID 7009464 mentions the issue, though not for Option 156. In
> that TID there is this:
> "Situation #2
> Migrate a working DHCP server with DHCP options that are of type
> "Text" to an OES server.
> Load the DHCP server service... it fails to load and gives similar
> errors to the ones listed above."
>
> Under resolution the TID says to delete and recreate the dhcp service
> object without the text option and it will load. That doesn't work for
> me as I still get an LDAP error pointing to the Shoretel_Boot unknown
> option. (I dare not try deleting it from the NetWare DHCP config and
> risk breaking the client's phone system).
>
> One of the options in the TID to fix this is to re-enter the data using
> the DNS/DHCP Management Console - but that didn't work.
>
> Here is the answer:
> First, the log files are misleading. The error message points to not
> being able to read the newdhcpservice object entry - but the problem was
> elsewhere. In fact the problem showed up in the logs even when there
> were no option 156 entries at all in any object inside the
> newdhcpservice or the newdhcpservice object itself. The problem
> existed in the NetWare configuration of the object for one of the dhcp
> subnets.
>
> Specifically, there was an illegal character in the text entry for
> option 156 - the # character was in there, like this:
>
> FTPSERVERS=172.30.43.8,COUNTRY=1,LANGUAGE=1,LAYER# 2TAGGING=1,VLANID=9
>
> If you look at the error log entry for syntax error you can see that the
> option 156 text stopped at the # symbol, and then default-lease-time was
> appended to the end.
>
> Removing the # symbol got things working.
>
> Craig Johnson
> (former Novell partner / sysop)
Thanks for taking the time to post the above as I'm sure it will help
someone else in the future.
Simon
Novell Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

Advice pls OES Linux cluster iSCSI drives separate NIC

In order to improve backup performance I am thinking of connecting our iSCSI drives (on Synology NAS box) to the 2 OES 11 Cluster servers via their second network cards. I.e. the iSCSI drives will be on a separate network so the data is not travelling over the same network twice in order to get to the backup server (Backup Exec on Windows).
I would welcome general comments on any pros and cons of this idea
Not being a network expert I am not sure how I can do this. As I understand it the second network cannot be in the same subnet as the main network or confusion reigns. However my cluster resources will have to be in the main subnet range. Is it that the iSCSI portal addresses can be on a different subnet but everything else is on the main subnet? Will I have any issues if I change the IP addresses of the iSCSI Initiators?
Thanks in advance

Originally Posted by NickHoare
In order to improve backup performance I am thinking of connecting our iSCSI drives (on Synology NAS box) to the 2 OES 11 Cluster servers via their second network cards. I.e. the iSCSI drives will be on a separate network so the data is not travelling over the same network twice in order to get to the backup server (Backup Exec on Windows).
I would welcome general comments on any pros and cons of this idea
Not being a network expert I am not sure how I can do this. As I understand it the second network cannot be in the same subnet as the main network or confusion reigns. However my cluster resources will have to be in the main subnet range. Is it that the iSCSI portal addresses can be on a different subnet but everything else is on the main subnet? Will I have any issues if I change the IP addresses of the iSCSI Initiators?
Thanks in advance
Since searching for cluster advice regarding iSCSI brings up this post near the top (!) I thought it worthwhile asking this secondary question to make this thread more of a reference.
Looking at previous OES Netware guide to using iSCSI in a network (8 years old but the closest thing to what I was looking for) it suggests that the iSCSI target (I think I mean initiator here - volumes are on a NAS box) is set up as a cluster resource with associated load and unload scripts. The documentation for iSCSI implies, but does not state clearly, that the iSCSI initiators should all be set up and connected beforehand. Presumably the assumption is that automatically or onboot connected initiators would already be connected.
Seeing as I hope not to have to do much with the system for weeks on end I am concerned that something could happen to the Nas box/network etc whilst the servers remained up so that connections would be lost at some point. Come the failover the iSCSI targets would not be there so all pool resources would fail to connect.
To that end I want to add, and I think as separate resource, a script to attempt to connect the iSCSI initiators in case they are not connected but not to fail if they already are. My proposal is this
#!/bin/bash
. /opt/novell/ncs/lib/ncsfuncs
ignore_error iscsiadm -m node --loginall=automatic
exit 0
which seems to work. In our simple 2 node network I may as well connect all with the advantage that the script does not need to be changed if we add further pools. (we have 2 pools each with 2 volumes which goes against some unexplained 'best practice' notes in the documentation). No point in testing for failures which might be hard anyway as there is presumably an error if they are already connected.
The unload script just has exit 0 .
Any comments or issues I should be aware of?

NDPS printer in OES Linux

I setup a lab with OES on SLES9 and setup a iPrint printer and it works
fine but how do I get it to show up when I try to add it from a
workstation with the Novell client and I select Add Printers >NDPS
Printers > NDPS Controlled Printers > Browse the tree but no printers
show up.
I can get add it through the maptool but I hoping to use NDPS first and
then migrate the users to iprint later.
Any help would be great.
Randy

Randymacfarland,
It appears that in the past few days you have not received a response to your posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
- Check all of the other support tools and options available at http://support.novell.com in both the "free product support" and "paid product support" drop down boxes.
- You could also try posting your message again. Make sure it is posted in the correct newsgroup. (http://support.novell.com/forums)
If this is a reply to a duplicate posting, please ignore and accept our apologies and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Where is settings.txt for PXE on OES Linux

Hello,
I am trying setup automated imaging using PXE. I can boot the
workstations with PXE fine but it says server 0.0.0.0 is not found. I
think I need to specify the default server like i do in the settings.txt
file on teh boot CD. but I can't find that file for PXE on the server.
Anyone know where to look?
Thanks,
Aaron

On Wed, 18 Jun 2008 14:44:27 +0000, Kurt Finlayson wrote:
> Aaron Z wrote:
>> Hello,
>> I am trying setup automated imaging using PXE. I can boot the
>> workstations with PXE fine but it says server 0.0.0.0 is not found. I
>> think I need to specify the default server like i do in the
>> settings.txt file on teh boot CD. but I can't find that file for PXE
>> on the server. Anyone know where to look?
>>
>> Thanks,
>>
>> Aaron
>
> PXE usually does not use that, but the file is found in /srv/tftp/boot
Thats was it! its working now. thanks.
Aaron

Mount OES Linux NSS to remote OES Linux NSS?

Have an issue where I dont have an evault backup agent on a new server I created yet. Both servers are running NSS and both are Oes2sp2. Is it possible to mount a (ready only?) directory from one server so it shows up on the other and is able to be backed up?
"fs-storage" is the one with the evault agent
"fs-attorney" is the remote server i want to backup. (fs-attorney/media/nss/DATA/atty
DATA being volume name.
Thanks

Originally Posted by joebrug
Sorry to dredge this old thread up, but did a search and I'm getting this same issue.. Trying to restore a groupwise account across the WAN to a remote location and randomly getting the Input/Output error for the NCP mount.
Kevin, have you experienced the same issue with restores? and did you fix with the auto mount?
I get a lot of "items added to download" in the post office logs.. then things just seem to stop. no more information in the log files and the threads just seem "stuck".
Hey Joe,
Yes, lately (maybe the last 3 months or so) we've had issues even across the LAN (like two servers sitting next to each other) where ncpmount just "disconnects". This makes restoring things REALLY fun (not!!)
I'm not sure if it's maybe the watchdog packets killing the connection or what.
I've not tried the automount thingy yet. I forgot about it. Anyway, just printed out the stuff and we'll give it a whirl.
Note: This is with OES2 SP3 32 and 64-bit. I've even tried patching things to the latest patches to no avail.

Communication between the DNS/DHCP Manager and OES Server

No communication between the DNS/DHCP Manager Console and OES server (status,start,stop)
The screenshot shows the tab "DHCP (OES Linux)" in the DNS / DHCP Manager console
in the bottom of the image it shows the state of the DHCP servers.
allDHCP.JPG
The dhcp service is started on all these servers
You can see that the status is known only for four servers.
The button "start/stop DHCP service" works fine on this servers and
the dhcp service can be canceled and also restarted
But the status of the "dhcp service" is not recognized for all the other DHCP servers
and so we can not start or stop dhcp service on these servers.
All servers were installed at different times (last three years) with OES11 and
are upgraded to OES11SP2 with all patches.
The server keto (DHCP_keto) is a new installation OES11SP2 few days ago.
All OES servers were set up identically from me. LDAP, LUM, DMS, DHCP works fine.
Which service on the OES server is responsible for
communication (status indicator) between the DNS/DHCP Manager and the OES serve?
How the status query is performed by the DNS/DHCP Manager?
How can I test the communication to the server on the client (console)?
Which configurationfiles I should be compare on the server?
Thanks in advance
Gernot

gernot,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://www.novell.com/support and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Forums Team
http://forums.novell.com

Free OES help available. Please read before posting.

Welcome to the OES Linux Storage and Backup forum.
Here is a list of free OES resources to help you answer your questions and resolve your issues.
Current OES Documentation
Recent Technical Information Documents (TID) - Open Enterprise Server
Open Enterprise Server Cool Solutions | Novell User Communities
Open Enterprise Server Wiki
The Novell Knowledgebase
Open Enterprise Server Product page
Novell Consulting Best Practices Guide: Automated Installation, Configuration, and Update for OES 11
You may be entitled to free installation support within thirty days of purchasing the product or you may be able to open a Service Request to obtain help with your issue at no additional cost if you have purchased maintenance and it is still current. Please refer to the following to see if you are eligible.
Support: Submit a Service Request: Details
Customer Center
Novell Services
If you still require assistance from our forum volunteers, I encourage you to read the Novell Forums FAQ for posting guidelines. Be sure to post in the appropriate forum.
These are the OES: Linux sub-forums: Administration, Install, Networking, Printing, Storage and Backup, Linux Web Services, and, Domain Services for Windows.
If you know or suspect you have a Linux issue, you may find the help you seek in one of the SUSE Linux Enterprise Server forums.
In addition to any other information you feel is relevant, please include the following with your post using [CODE] tags (i.e. the # formatting option) to make the output more readable:
The exact error messages, if any, as they are shown. (You may find other messages and clues in the log files located in /var/log, especially in /var/log/messages.)
Output from these commands run from a command prompt.
cat /etc/*release
uname -a
Note: Do not reply to this post as this thread has been closed. If you have any comments, or wish to report an issue concerning this post, create a new thread in Feedback About These Forums and be sure to refer to this forum.

I can understand your point of view and I respect it in regards to Small Basic being a learning language. None the less, let me make a suggestion that would be more ageeable, I think, to different kinds of people. Why not make different versions
of this new language: version 1 for beginners that I heard would be out by the end of this year,
version 2 for intermediates and version 3 for more advanced programmers. All this would culminate to the Visual Basic language. These 3 versions would smoothe out the gap between SB and Visual Basic. Your new programmers would
evolve at the same time your versions would come out and Microsoft would have a long term policy of loyal programmers.

ZEN7 on OES Linux

Similar Messages

Maybe you are looking for