WAAS Printing...

Unanswered Question
Jan 4th, 2008
User Badges:

I've set up WAAS printing services for a client. I'm facing the following problem though...


When the clients are logged-in locally, printing services are working fine at the branch offices. But once they are logged-in on the domain, i get a msg saying that a policy is preventing them to print on this printer.


Correct me if i'm wrong but, this has to do with the WAEs Print servers not being added to the Active Directory. I haven't found in any documentation how exactly to do that. Do u just add the WAEs with their NETBIOS names as machines in the AD? Also, the hostnames differ from the NETBIOS naming convention that the client wants to use in his domain. Cisco says that Netbios and Hostnames should match when the devices are to be added in the AD. Will it cause any problems if i just rename the WAE hostnames to match the Netbios names desired?


Thanks

Panos.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Zach Seils Sun, 01/06/2008 - 18:09
User Badges:
  • Cisco Employee,

Panos,


With these types of policies in place, the WAEs providing print services will need to be joined to AD domain. You can use the following instructions to accomplish this:


http://cisco.com/en/US/docs/app_ntwk_services/waas/waas/v4013/configuration/guide/admin.html#wp1042876


As far as the hostname you use, we do recommend that you use single hostname (DNS and NetBIOS) for the WAE. You can change the hostname of the WAE to match the desired NetBIOS naming scheme.


Zach



p.stavrinou Tue, 01/08/2008 - 05:55
User Badges:

OK Zach, will give it a shot and let you know on the outcome.

p.stavrinou Fri, 01/11/2008 - 03:03
User Badges:

Zach,


We have gone through the process of registering the WAEs in AD. We have created two groups in the AD with Global user scope, with the group names matching the ones entered in the fields under General settings>Windows Domain tab. In realm field we entered the fully qualified domain name, the domain controller name as key distr. center and the fully domain name of the domain controller in the domain controller field. Upon entering domain admin credentials and waiting a few minutes, the registration process failed with an error msg on the popup status window saying : "No registration record was found." Any idea what the problem might be?


Panos

p.stavrinou Fri, 01/11/2008 - 06:58
User Badges:

Zach,


Just a couple of more things to the picture...Attached is a log from the debugging msgs i've been getting during the registration failure, as well as a screen capture with the domain settings screen. It seems that we're having a problem with the Kerberos authentication during the registration(kerberos_kinit_password [email protected] failed: Cannot find KDC for requested realm [2008/01/11 13:51:01, 0] utils/net_ads.c:ads_startup(191) ads_connect: Cannot find KDC for requested realm) Any ideas what could be going wrong?


Panos



Zach Seils Mon, 01/14/2008 - 23:08
User Badges:
  • Cisco Employee,

Panos,


Don't worry about configuring the group names -- you don't need those for what you are doing.


In the configuration, the realm should be just the DNS suffix of you AD domain -- lim.tepak.int in your example.


Zach



p.stavrinou Tue, 01/15/2008 - 05:40
User Badges:

Zach,


Thanks for the tip :) The registration was succesfull and the users can print on the WAE print servers now.


However there are a couple of questions raised:

1. When you press the "show authentication status" button i'm getting the msg in the attached image. Why's that?


2.When new WAE will be added in time, this procedure has to be manually repeated for registration right since the credentials are not saved on the CM? Will this have an impact on the already registered devices if they belong to the same group(i.e AllDevicesGroup)?


3.Regarding the CIFS optimization, is there any way that you can display information about cached objects per filename?


Panos







Attachment: 
Zach Seils Tue, 01/15/2008 - 06:59
User Badges:
  • Cisco Employee,

1. I'm not sure. Let me look into it and report back.


2. It shouldn't, but let me test to confirm.


3. Today this is not possible.


Zach



p.stavrinou Tue, 01/15/2008 - 07:15
User Badges:

Ok Zach, will be expecting ur feedback. Thanks again for your prompt replies.


Panos

p.stavrinou Tue, 01/22/2008 - 05:08
User Badges:

Zach,


Added another WAE for print services. It runs 4.0.7.b.46, will be upgrading to 4.0.13.23 tomorrow. Registration is sucessfull and i can see the device in the AD. However, i cannot print on the print server. Attached is an alarm i'm getting on the device. Could this be gone by upgrading the device or do we have any sort of h/w issue? The hdd on the module appears to be healthy.


Panos



Zach Seils Sat, 01/26/2008 - 02:44
User Badges:
  • Cisco Employee,

Panos,


I would need to see the crash file to determine what happened. Can you check in the core_dir directory and see what version is used in the filename? If it is something before 4.0.13, just delete the file and let me know if it happens again after the upgrade.


Zach


Zach Seils Sat, 01/26/2008 - 02:42
User Badges:
  • Cisco Employee,

1. The last authentication status is saved to a local file on disk. It looks like when the 'Show Authentication Status' button is used from a device group the file isn't created. I'll following up with Engineering on this.


2. Looks like the registration happens again. I'll follow up on this as well.


Zach


p.stavrinou Sat, 01/26/2008 - 05:58
User Badges:

Zach,


Have upgraded the version to 4.0.13 and upon reboot the msg was still there. Oddly, the CIFS accelerator was working but still had issues with printing. Problem was resolved after switching the module with another router. Printing now works as well. So i consider the problem being solved :)


Just please get back to me on the authentication status msgs since the client would like to know what causes these to be displayed. Thanks.


Panos

Zach Seils Sun, 01/27/2008 - 09:28
User Badges:
  • Cisco Employee,

The alarm won't go aware until you delete the file in the core_dir directory.


I'll let you know what I find on the authentication messages.


Thanks,

Zach


p.stavrinou Mon, 01/28/2008 - 02:26
User Badges:

Ok Zach. Will be waiting for your feedback. Thanks.


Panos

p.stavrinou Thu, 01/31/2008 - 00:53
User Badges:

Zach,


We have an issue again. We have added some new print servers in the network but when we attempted registration we got the msg in the attached document. Also, we attempted to unregister a device from the AD through the CM GUI, but the device does not unregister from the AD. Since we are using Kerberos for authentication, isn't this process supposed to remove the registration/addition of the WAEs from the AD where they were added as computers?


Panos.



Zach Seils Fri, 02/01/2008 - 04:40
User Badges:
  • Cisco Employee,

Panos,


Can you resolve the domain name from the WAE:


dns lim.tepak.int


?


Zach

p.stavrinou Fri, 02/01/2008 - 06:00
User Badges:

Yes Zach. I can resolve the DNS name from all WAEs. No dns issues here since i can resolve all the printer names as well.


Panos

Zach Seils Wed, 02/06/2008 - 03:19
User Badges:
  • Cisco Employee,

Panos,


Can you please try running the following command and sending me the output:


script execute wdd.sh.signed ads LIM.TEPAK.INT


where and are the credentials used for registering the WAE in AD.


Thanks,

Zach



p.stavrinou Thu, 02/21/2008 - 06:13
User Badges:

Zach,


Can you provide any details on what this script will actually do? The client has concernes if it will affect anything on the AD domain controllers?


Panos

Zach Seils Thu, 02/21/2008 - 07:55
User Badges:
  • Cisco Employee,

Panos,


The script just runs some diagnostic commands on the WAE. It should not have an adverse effect on the domain controller.


Zach



p.stavrinou Fri, 02/22/2008 - 00:11
User Badges:

Ok Zach thanks. Will run it and send you the outcome.


Panos

p.stavrinou Tue, 03/04/2008 - 08:26
User Badges:

Zach,


Sorry for the long delay. The client had some delays in running the scripts. Anyway, i'm attaching the outputs from 2 WAE print servers.


Panos



Attachment: 
Zach Seils Fri, 03/07/2008 - 10:33
User Badges:
  • Cisco Employee,

Panos,


The output ("Cannot find KDC for requested realm") indicates a name resolution issue. Can you verify (again) that forward and reverse lookups for the domain suffix work?


Zach



p.stavrinou Sat, 03/08/2008 - 16:17
User Badges:

Zach,


Name resolution, both forward and reverse lookup, is working fine. The strange thing is that although we are getting these msgs, the printing feature is working just fine.


Panos

Zach Seils Wed, 03/19/2008 - 19:50
User Badges:
  • Cisco Employee,

Panos,


This means that some process has crashed and restarted. The crash file is written to the local1/core_dir directory. Can you send me a copy of that file? From that we can determine what the process was.


Zach



p.stavrinou Thu, 03/20/2008 - 00:51
User Badges:

Zach,


The only file under the local1/core_dir directory is the one i'm attaching. I hope it's the one you requested.


Also, is there a chance that these crashes will be fixed with the new 4.0.17 software? In understand there have been issues with 4.0.15 and has been withdrawn(although we're running 4.0.13). Thanks.


Panos



Zach Seils Fri, 03/21/2008 - 21:20
User Badges:
  • Cisco Employee,

Panos,


I don't see any existing defects for this issue. Can you reproduce the crash?


Note: To remove the alarm from the CM, delete the file from the core_dir on the WAE.


Zach



p.stavrinou Sat, 03/22/2008 - 09:14
User Badges:

Zach,


This crash has not impacted neither user experience with WAAS nor the printing services. They client has not reported any issues with either of these. The statistics on the CM appear to be normal with good acceleration values.


Deleted the files on the appliances and will let you know if this issue resurfaces. Meanwhile, i will upgrade to the latest 4.0.17 code. Thanks.


Panos

Panos,

I understand that you are using WAAS Printing services...

I was wondering if you have encountered any problems or issues now that you have everything configured.

I am looking at implementing WAAS Printing too but want to know how reliable it is.

Do you happen to know how many printers it can service? I understand it only has 1 GB Spool limitation and wondered what would happen if many people began sending print jobs larger than that to it...would it crash?

Thanks,

Kevin

Actions

This Discussion