SA540, 2.1.18 and mDNS

When I upgraded from 1.6X (3?) to 2.1.18 at one site, the wireless macs seemed to stop working. Problem is failed DHCP and DNS. I can fix IP addresses and DNS still fails, if I browse without DNS, everything works fine. Did something change with NAT, DNS Forwarding or Bonjour handling? No other changes, I can roll back firmware and make things work fine.
All wired devices work fine.
AP's are connected to closet switches which in turn go to an aggregation switch and then to the router. All switches are ESW-540's. AP's support multiple VLANS. The devices/SSID effected here is the default vlan. Other vlans work okay but they don't have any Mac traffic either.
If I tunnell all the traffic through the WLAN controller then they work fine (looks like wired device to router?) except for a Mac Book Air.
Any bugs that got fixed that would effect this (i.e. I had a setting that should have broken it before but it broke...)
Anyway to post my settings for review without taking 120 screen shots?

Hi ,
Please contact the SBSC team to help you resolve this. Their phone number is:1-866-606-1866.
The following page contains the pertinent contact list.
http://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html
wei

Similar Messages

SA540 CPU 100% Utilization AND VPN Failures

I am having regular trouble with my SA540 in that the VPN tunnels are failing. When I check the VPN tunnel I also find that the CPU utilization is listed at 100%.
Any suggestions?
Gregg

Hi,
Having 100% on some of your CPU is normal on the IPS platform.
The device is using it's idle cycles to prepare for the handling of the incoming packets and to reduce the delay it will introduce on their path so it is expected to get this even when under low load.
If you want to have a better idea of the capacity % of your IPS you are currently using, you should have a look at the Inspection Load value. Looking at the data you provided, you are around 25% at the moment.
For the rdep timeout message, it seems to be a software issue. Looking closer at the picture you attached, we also see "Analysis Engine Status: Not Responding".
It is a bit difficult to troubleshoot those on CSC so I would advise you to open a TAC case if you want to know the exact root cause.
What I would advise is to upgrade to the latest 7(0) code which is I believe 7.0(5a)E4 since the issue is most then likely fixed in this version.
If you are looking for a quick fix, a reboot of the IPS should clear this but the problem will most then likely come back later.
Regards,
Nicolas

APPLETV and mDNS - Turn OFF mDNS it works, Turn it on it doesn´t?!?!?!?

Hi guys!
I´m having a strange morning. We switched from 7.2.x code to 7.4.121.0 on our 5508 WLC. And Today I get a call that the apple tv´s aren´t visible any more.
Quick check into the MDNS profiles, I see each and every one. Quick check on my iphone to my test appletv - that works too. But it is the only ATV I can actually see.
- I can only see the atv when it is connected to the same Accesspoint, if I roam it vanishes.
- If I turn OFF the MDNS Settings - I see every atv in the building!!!
I configured everything according to: http://www.cisco.com/c/en/us/td/docs/wireless/technology/bonjour/Bonjour74.pdf but somehow it is not working.
Settings:
(yes the mDNS global is enabled in the tests ;) )
I can see the ATV´s on the WLC:
When it is enabled I can only see the Apple tv that is connected wirelessly to the same AP I´m connected to! So none of the wired devices!
I have enabled the DNS Snooping in the advanced settings for the WLAN. I have also found an extra MDNS Snooping for the Interfaces itself, which wasn´t activated. But activating it, didn´t help a thing. I also tried deactivating the VLAN Multicast feature that was needed in 7.2.x but also to no avail.
HELP! Any Idea what might be running amok here? Everything was working without a hitch in 7.2.x and I thought the 7.4.121.0 would be a blast, because easier, better and such :D Thanks alot for your help!

o.k. thats abit stupid. I had a brain freeze. But just to follow up on this:
If your MDNS Profile that is used for the snooping DOESN´T have the airtunes part included. It won´t work. Just because the general option is choosen, doesn´t do diddly swat for the wlan itself. Guess thats an error I just had to make ;)
Problem solved!

MDNS and Apache NameVirtualServer

I'm trying to setup a set of developer machines with multiple websites on each, and accessible to other machines on the local network.
Currently I'm using mod_bonjour and very high port numbers (computer.local.:8000) to allow for multiple sites, but I'd prefer if I could resolve by name.  I can currently do site.localhost resolution, but it is only accessable to the machine it's on, which I'd prefer to do is to use mDNS to resolve *.computer.local domains, and then configure apache to handle them (site1.computer.local, site2.computer.local), but I can't figure out how to get the mDNS to handle the subdomains.
I realize the simple solution to this would be to setup an internal nameserver that handles .local or .site dns names, but I'd prefer a zeroconf solution.

I'm not a "Bonjour folk", but I have been disliking it a lot lately.
OS X Lion does indeed appear to have a problem with .LOCAL, bonjour, and mDNS. Apple's recommended AD integration vendor (Centrify) has had this confirmed with multiple clients (of which I am one of the lucky ones). This also affects the login/AD access times. Their support believes there is a work around... all I have are the generalities right now. I am supposed to get details (or a new job) soon. You can get me offline for the rest:
1.   Add primary zone ‘local’ in DNS server
2.   On Mac , disable IPv6
3.   Set the mdns_timeout as ‘1”
4.   Try to login as SMB network home user and try to mount SMB share folder with normal AD user

Mdns and dot local

Bonjour folks (sorry)
I'm a seasoned 'Doze server admin and I've just discovered Bonjour and more importantly mDNS and how it can be cause problems if you follow MS's recommendation to use a .local domain name.
As the great majority of networks I deal with personally use .local are there any special considerations for Lion or will it actually query name servers if you try to integrate a Mac into a Windows environment?
The reason I ask is I'm finding Active Directory support to be too slow for a production environment and I *think* this could be our problem.
Any pointers or fixes (rather than fudges ) will be much appreciated.
Ta,
Rob

I'm not a "Bonjour folk", but I have been disliking it a lot lately.
OS X Lion does indeed appear to have a problem with .LOCAL, bonjour, and mDNS. Apple's recommended AD integration vendor (Centrify) has had this confirmed with multiple clients (of which I am one of the lucky ones). This also affects the login/AD access times. Their support believes there is a work around... all I have are the generalities right now. I am supposed to get details (or a new job) soon. You can get me offline for the rest:
1.   Add primary zone ‘local’ in DNS server
2.   On Mac , disable IPv6
3.   Set the mdns_timeout as ‘1”
4.   Try to login as SMB network home user and try to mount SMB share folder with normal AD user

Local Switching, mDNS Snooping and Chromecast

Hello everyone,
we have a Cisco WiFi setup at our company constisting of one WLC (2504) and 5 access points, 4 of which are in the main office and one at a remote location (connected via an IPsec tunnel). The remote AP is configured to FlexConnect mode, and we have set up a staff WLAN using 802.1X auth and local switching. So far, everything works perfect.
However, we now want to support Chromecast devices in our wireless network. I have setup a new WLAN with WPA2-PSK authentication for those devices, added the "Googlecast" entries to the mDNS profile and activated mDNS Snooping on this WLAN. This appears to be working as well, at least I can see the corresponding entries in the mDNS -> Domain Names tab (Chromecast switched from multicast/SSDP to mDNS recently).
However, clients in the staff WLAN are not able to see the devices. My guess is that I would need to also activate mDNS snooping on the staff WLAN, but of course this is not possible because of local switching being enabled.
I tried to create two different AP groups, one for the local APs and another for the remote one. Then I duplicated the staff WLAN, with the idea of deploying one copy on the local AP group with local switching disabled and mDNS snooping enabled and the other copy on the remote AP group, enabling local switching and disabling mDNS snooping. My idea was that this would allow the employees at the local office to use the Chromecast devices, but unfortunately it's not possible to configure two WLANs with the same SSID and L2 security, even if they're not on the same AP / AP group.
Another solution would just be to create a separate WLAN for the remote AP, but that would require to push another profile and inevitably result in confused employees when they first visit the remote branch.
Is there any way to make our Chromecasts work while still using the same WLAN for both locations? Any pointers are greatly appreciated.

I'm not 100%sure about the details and why that works this way. But u can create two SSID as long as u use an ID higher than 16. So start at 17 and it works, maybe that has something to do with the default group they will not belong to..
comming back to your 2504...I see no way to use an ID above 16 because that's the max it supports.
So, please have a look at that Guide for Chromcast, as I run through i see that it hase maybe nothing to do with mDNS..
http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-6/chromecastDG76/ChromecastDG76.html
Br,
Sebastian
pls. rate if helpful

Info about MDN

Hi all,
We are sending an 850 transaction to our supplier, and we are receiving an MDN back from them. If we open details of MDN it showing
Collaboration
Revision
Business Action Acknowledgement
Revision
Process Protocol
Exchange Protocol AS2 - 1.1
B2B Message Id 0A1648201266BFC6E210000020FA9300-1
Protocol Message Id <CLEOAS2-20100126_190245860@EMRSNT_PSKLUSB2BAS2T.pltc501.logistics.penske.com-D>
Protocol Collaboration Id
Receive Time Stamp January 26, 2010 6:56:52 PM
Send Time Stamp January 26, 2010 7:02:41 PM
Acknowledge Mode None
Reply Mode Async
Agreement Emerson_Penske_Agreement
Message Date Time January 26, 2010 6:56:52 PM
Error Code
Message Type
State Complete
Remaining Retry 3
Acknowledge Type Document Exchange
Direction Inbound
Time To Acknowledge
Sending Trading Partner Penske
Wire Message View
Correlated Message View
Payload Payload
In these details, just i want to know
Receive Time Stamp January 26, 2010 6:56:52 PM
Send Time Stamp January 26, 2010 7:02:41 PM
What are these timing. Recive time stamp is : I guss this is the time we reached the MDN, but what is Send time stamp
Regards
cnu

Hi,
In MDN details we have :
Receive Time Stamp January 27, 2010 12:17:35 PM
Send Time Stamp January 27, 2010 12:23:24 PM
Acknowledge Mode None
Reply Mode Async
By seeing above they recived at "January 27, 2010 12:17:35 " and they send MDN back at "January 27, 2010 12:23:24 PM", If Yes, then why it taking 6 minutes to receive MDN back ..
If we see the reports in business message tab:
it shows we send po at January 27, 2010 12:17:29 PM
and we received MDN back from them at "January 27, 2010 12:17:35 PM".... these are timing of PO and MDN... ten what are the details in MDN.
Regarsd
cnu

MyDAQ fails Self-Test and will not work with any software

I cannot get the myDAQ to communicate properly. I did everything I could to make sure that the device was detected by the computer. It shows up in Device Manager under Data Acquistition Devices as NI myDAQ and in NI MAX as "myDAQ1", but I receive errors when trying to use it with any NI program.
Trying to self-test or reset the device in MAX gives these errors:
-The self test failed. -88705 The specified device is not present or is not active in the system. The device may not be installed on this system, may have been unplugged, or may not be installed correctly.
-There was a problem resetting the device. Error code: 80040383.
It also gives this error when trying to use the Elvis Oscilloscope:
-Error -200324 occurred at ELVISmx_DAQmx Create Channel (AI-Voltage-Basic).vi:1
Possible reason(s):
NI-DAQmx is unable to communicate with the device. Make sure the device is present in and accessible to the system, is not currently being reset, and is not reserved by another driver such as Traditional NI-DAQ (Legacy).
I have uninstalled and reinstalled and repaired all installed NI products twice. I updated to NI-DAQmx 9.8.0 and am using NI Elvis 4.5. I have checked NI Device Loader and mDNS Responder Service in Services and everything is running properly. I have also tried Reset Configuration Data in NI MAX several times. I turned Fast Startup off as suggested in one article. I have tried plugging it into every single USB port on my computer; all 8 of them. The blue led is on when plugged in, but I cannot figure out why it will not work with any of the software. I am running Windows 8 Pro 64-bit. Also, it completely works on the school computers running Windows 7 without any problems. I would like to have it functioning with all the NI software purchased, but all I want to do is use the oscilloscope software for now. It has honestly been way too much work and a huge loss of time for something that should work out of the box. Please help me resolve this, thanks.
Attachments:
ni_support.zip ‏341 KB

Hi chaka123,
I had already read that article so it wasn't anything I hadn't tried. I did, however, uninstall both NI DAQmx and NI ELVISmx, ran the registry cleaner and then plugged my device in. Now it shows up as USB Flash Firmware Updater. This is actually what it showed the first time I plugged this in out of the box. After much troubleshooting I was finally able to get it to at least recognize it as a myDAQ. This is problem I know others have had.
To answer your questions:
Does the Test Panels work at all?
I am not sure, I didn't try it before uninstalling. Now the Test Panels isn't an option because it is recognized as the Flash Firmware Updater.
Have you tried to delete the device in MAX?
Once again, I cannot because it shows up as Flash Firmware Updater.
Which is the color of the icon on the left side of “myDAQ1”?
It was green before the uninstall. Now it shows the USB symbol.
I tried deleting the driver. When I plugged the device back it, Windows started automatically trying to load a driver for it. Now it shows as NI myDAQ with a yellow exclamation symbol. In MAX it shows as NI myDAQ with a USB symbol. Under Driver Details it says "Windows does not have a driver associated with your device."
What folder can I manually point Device Manager to in order to load the correct driver?
Attachments:
devicemanager.PNG ‏40 KB

DNSService error and self expanding console.log file

Just like misskool, I had a problem with self-expanding console.log files. As suggested by roam, I erased the com.apple.iTunes.plist file to fix the issue. Unfortunately, 2 days after, the same problem started again. I noticed it happened soon after I tried (without success) to establish a mac OS 10.3.9 to mac OS 10.4.9 wireless network - either that or the re-activation of AppleTalk on my iBook. The error message in the console.log file is a repeated one-liner :
DNSServiceProcessResult() returned an error! -65537
The original advice from roam worked until I tried to network my two macs. In his idea, iTunes was the probable origin of the problem. Is it ?

The mDNS error message was associated with an iTunes update, though that is not to say it is caused by iTunes though it may well have. The error is from the mDNS service, a system wide network service, which looks for available services on the network.
I don't know what is causing this error but it has been known about since 2005, evidenced by this thread. It is a highly technical discussion,
http://lists.apple.com/archives/Bonjour-dev/2005/Jul/msg00023.html
which talks about the error occurring when two ethernet interfaces are active, but does not err when only with one. It is possible this observation is linked to your experience trying to network two Macs.
Click on the Next Threads on that page to read more.
Another thing to note is that the error code given is general and undescriptive, where one poster writes " Normally when you see that error it means that mDNSResponder (mdnsd) crashed." ... but there is no specific meaning given to the error code as to why it did.
So it's a bug but I cannot explain why it occurs or what role the iTunes update played in bringing it to the fore.
If it continues to be a problem with the same error message printing in the console, open Activity Monitor and mDNS should be active there and kill that mDNS Process.
As i have no iTunes updated, and do not want to try and create this error, I'll leave it up to you to try and determine some causes and effects regarding the renegade process of mDNS.

Message retry count for the message has been exhausted

Hi,
I am using 'Custom Document Over Internet' with HTTPS as transport protocol. I have set the acknowledgement mode to Sync in order to receive the synchronous response. B2B is able to post the HTTP request successfully and in turn it receives a synchronous response and a MDN message. At the initial stage, after posting the request it shows the state as 'WaitForAck' for request message and for response and MDN messages, the state is completed.
After some time when we check the state of request it is changed to 'Error' with the error message as 'Message retry count for the message has been exhausted'. We have not set the retry count and retry interval and so after retrying for 3 times with an interval of 120 minutes it is showing error state as it is not able to correlate the incoming response to the corresspoding request. We have tried the option of setting the Message id of the request in 'replyToMsgID' parameter of response header and tested the flow. But still I am facing te same issue. Please help me to resolve this issue.

Hi Anuj,
The property mentioned by NandaGopal has already been added in tip.properties file. I sent the B2B logs in debug mode and tip.properties file to your mail id. Please have a look into that. The result of opatch lsinventory command is
Result:
Installed Patch List:
=====================
1) Patch 9234704 applied on Fri Jan 15 16:41:12 GMT 2010
[ Bug fixes: 8870866 9143036 ]
[ This patch overlays patches " 8703410 " ]
[ This patch needs patches " 8703410 " as prerequisites ]
2) Patch 8703410 applied on Thu Jan 07 17:56:08 GMT 2010
Unique Patch ID: 11901808
[ Bug fixes: 7652646 7497854 7664370 8708445 7661101 7007789 6352814 6802446 7665607 7641078 6496457 6013963 8330151 7305413 8619657 7460584 7529893 7458954 7020996 8393885 8210401 6329207 6740403 7126458 6511970 8783577 7379065 7230993 8704965 6774631 7198642 8309511 8392729 7661769 7605518 7479148 6733262 8349002 6736026 7322333 7242500 7239355 8746561 8344645 8451004 7645440 6747966 6369424 6737334 8339176 6774134 7046561 6412124 7210461 7506319 8630406 8235175 7258882 7184318 6453359 7456866 7673646 6043277 7457597 6769895 7193710 8239170 7668247 8404955 8612841 7261965 7132740 7485790 6518386 7305363 6852370 6433256 7673431 6764239 8360048 7501748 7379153 8281019 7498031 8216457 7046574 6875312 6754906 6656289 6417367 7658271 7556011 7000190 6979467 8594506 8691820 6852308 8475848 8518443 7600385 7211208 6732051 8524862 7461051 8263026 7609467 7379161 7672714 6353293 7157229 7594997 7211287 7034069 7563311 6822375 6640935 7359202 6769261 6919593 8601869 6029507 6974391 7139013 7518641 8605719 6817264 7501903 7496014 7576785 8666761 7130151 7322581 5523563 7680097 8508905 7241737 7660780 8480395 7660781 7191994 6924921 7672723 8432093 6800745 8703404 8540335 8507242 8608121 8217566 7481317 6639030 6200414 7529795 7354853 8475867 7376270 7303860 7016005 7678901 7368610 8992520 6881977 6016128 7033061 6397084 7672730 8703410 7709562 6449656 7045589 8508054 6491068 7378745 7643811 7435853 7615836 8707416 6447557 7379042 6940476 7670634 6950383 6764273 6962327 7478322 8546454 7157324 8871403 8862082 7184219 7672744 7164618 7672745 7230184 7576730 7590301 8746541 7261863 8327427 6769430 8295683 7526186 8298731 6414280 6139955 6646997 7692853 8233048 6794296 7457066 8552373 8225241 7706387 7204022 ]
3) Patch 4601861 applied on Fri Nov 14 04:24:08 GMT 2008
[ Bug fixes: 4601861 ]

SA 540 Firewall

Hi all,
I am having trouble configuring the firewall for the SA 540.
client 1 (160.222.46.154) ----- switch ------ sa 540 ------ cisco 887 W ------ client 2 (50.0.0.10).
client 1 can ping client 2, however client 2 cannot ping client 1. The default outbound policy (allow all) is set on the sa 540, and I have tried configuring a blanket ipv4 rule on the sa 540 to allow 'all' to 'any' (for all services) related to traffic from the WAN to LAN, and visa versa. The output from the logs are as follows:
Fri Jan 7 13:43:04 2000(GMT +1000) WARN FIREWALL 50.0.0.10 160.222.46.154 [firewall] LOG_PACKET[DROP] IN=WAN OUT=WAN SRC=50.0.0.10 DST=160.222.46.154 PROTO=ICMP TYPE=8 CODE=0
Component: KERNEL
Fri Jan 7 13:43:09 2000(GMT +1000) WARN FIREWALL 50.0.0.10 160.222.46.154 [firewall] LOG_PACKET[DROP] IN=WAN OUT=WAN SRC=50.0.0.10 DST=160.222.46.154 PROTO=ICMP TYPE=8 CODE=0
Component: KERNEL
Fri Jan 7 13:43:14 2000(GMT +1000) WARN FIREWALL 50.0.0.10 160.222.46.154 [firewall] LOG_PACKET[DROP] IN=WAN OUT=WAN SRC=50.0.0.10 DST=160.222.46.154 PROTO=UDP SPT=60737 DPT=53
Component: KERNEL
I set up a new vlan on the cisco 887 W, in the 160.222.46.x address space, and connected a spare port directly to the sa 540 and had no problem testing connectivity to any device via ping. Obviously the zone communication is LAN to LAN and firewall treats the traffice differently.
I assumed that creating an all encompassing rule to allow all trafiic, for all services, between the LAN and WAN (in both directions) would be equivalent to placing the appliance in PASS THROUGH mode?
Also there is no securtiy set on the 887 W or the switch.
Any help would be appreciated.
Regards
Marc

On closer analysis and with some help from Experts Exchange it did seem non sensical to have both the IN and OUT as the WAN interface, but I had literally exhausted every avenue possible bar 1- changing the routing mode to CLASSIC and configuring a static route (which was at a higher administrative level than my RIP advertised routes) and took preferece when forwarding the packets.
Now the SA540 firewall rules work as I would expect and I can route between all zones. To summise it appears as if the Double NAT from the router (887W) and then the SA540 was the issue, and the innability to configure any workaround in the interface of the SA54O firewall rules.
It really makes you appreciate the power of the command line and the full scope of CIsco's command line options. Does anybody know if (and how) it would be possible to configure Double NAT on the SA540?
Regards
Marc

SA 540 INBOUND FIREWALL RULES NOT WORKING

Hi all,
I am having trouble configuring the firewall for the SA 540.
client 1 (160.222.46.154) ----- switch ------ sa 540 ------ cisco 887 W ------ client 2 (50.0.0.10).
client 1 can ping client 2, however client 2 cannot ping client 1. The default outbound policy (allow all) is set on the sa 540, and I have tried configuring a blanket ipv4 rule on the sa 540 to allow 'all' to 'any' (for all services) related to traffic from the WAN to LAN, and visa versa. The output from the logs are as follows:
Fri Jan 7 13:43:04 2000(GMT +1000) WARN FIREWALL 50.0.0.10 160.222.46.154 [firewall] LOG_PACKET[DROP] IN=WAN OUT=WAN SRC=50.0.0.10 DST=160.222.46.154 PROTO=ICMP TYPE=8 CODE=0
Component: KERNEL
Fri Jan 7 13:43:09 2000(GMT +1000) WARN FIREWALL 50.0.0.10 160.222.46.154 [firewall] LOG_PACKET[DROP] IN=WAN OUT=WAN SRC=50.0.0.10 DST=160.222.46.154 PROTO=ICMP TYPE=8 CODE=0
Component: KERNEL
Fri Jan 7 13:43:14 2000(GMT +1000) WARN FIREWALL 50.0.0.10 160.222.46.154 [firewall] LOG_PACKET[DROP] IN=WAN OUT=WAN SRC=50.0.0.10 DST=160.222.46.154 PROTO=UDP SPT=60737 DPT=53
Component: KERNEL
Basically any connection identified as coming in from the WAN (i.e. IN=WAN) is dropped. I set up a new vlan on the cisco 887 W, in the 160.222.46.x address space, and connected a spare port directly to the sa 540 and had no problem testing connectivity to any device via ping. Obviously the zone communication is LAN to LAN and firewall treats the traffice differently.
I assumed that creating an all encompassing rule to allow all trafiic, for all services, between the LAN and WAN (in both directions) would be equivalent to placing the appliance in PASS THROUGH mode? There is no securtiy set on the 887 W or the switch.
Also is anybody could explain what 'SELF' means in the conttext IN=SELF or OUT=SELF it would be much appreciated. Firmware is latest.
Thank you.
Regards
Marc

On closer analysis and with some help from Experts Exchange it did seem non sensical to have both the IN and OUT as the WAN interface, but I had literally exhausted every avenue possible bar 1- changing the routing mode to CLASSIC and configuring a static route (which was at a higher administrative level than my RIP advertised routes) and took preferece when forwarding the packets.
Now the SA540 firewall rules work as I would expect and I can route between all zones. To summise it appears as if the Double NAT from the router (887W) and then the SA540 was the issue, and the innability to configure any workaround in the interface of the SA54O firewall rules.
It really makes you appreciate the power of the command line and the full scope of CIsco's command line options. Does anybody know if (and how) it would be possible to configure Double NAT on the SA540?
Regards
Marc

Seeburger adapter configuration

At my client place they want to send an orders idoc as an EDI document to customer,,Can any one please tell me how to configure seeburger adapter & the mapping for edi.
Advanced Thanks
Kum

Hi sati,
First you need to instal Seeburger BIC and then you should generate the XSD structure of the all yor documents.In Sebbburger BIC mapping designer is generate thes type of all the mappings1)E2X----EDI to XML and X2E ---XML to EDI etc.Seeburger BIC mapping desigener can take care all the tranformatiom of EDI to XML and XML to EDI.once instalitation is finshed, then you can chek with BIC mapping desginer .
Seeburger adapter is the B2B EDI Adapter.Seeburger adapter is also many types adapters:
1)BIC Adapter
2)Split997 adapter
3)AS2 adapter.Based on your usage you have to configure thes adapter.for example
AS2 sender adapte configuration:
1)AS2
2)Asynchor MDN Setting:
a)SSL Certificates and Clint certifactes.
b)SSL host name:HTTP Timeout,MDN Retry interval and MDN Retry count
c)use proxy
AS2 Receiver adapter:
a)HTTP:server ,port ,url and http time out
b)proxy:
c)AS2:Compress,Sign.Encrypt,Sign MDN use proxy and Xi Message
Seeburger Adapter have more funcations:it is very good to Moniter Message.
1)Archiving
2)Message monitor
3)message Spliter
4)Mapping Variable
5)Resource manger
If you nedd any more information regarding the Seeburger ,send your maild then i will send the some more docs to you.
Regards,
Ramesh

Push out Adober Reader changes to Macs

I have a network with both Windows and Mac clients that use Adobe Reader. I already know how to use Active Directory Group Policy to push the necessary registry changes so that my Windows based clients can have their Adobe Reader settings updated.
However, for my Mac users where the settings exist in .plist files, I have been searching for a way to centrally update these same settings (I'm interested in pushing out security related settings when Adobe releases security advisories saying that the mitigation is to ensure that certain settings are in place until a full blown patch is released).
Does anyone know how to push out .plist settings changes from a central point similar to what AD Group Policy allows with registry changes?
Thanks,
Brandon

I ran into this issue some time ago as well and wrote just such a script!
Here's an exerpt from my documentation:
Lastly we need to add the Printer via the command line. Here's how:
First thing we need to do is copy the PPD file to the correct location. By default it's in /Library/Printers/PPDs/Contents/Resources/
The PPD in question can be found specifically by typing lpinfo -m This lists all of the printer drivers available to cups.
You must copy the gz file using sudo. It needs to be copied to /usr/share/cups/model/
The copy command looks like this:
sudo cp /Library/Printers/PPDs/Contents/Resources/HP\ LaserJet\ P3010\ Series.gz /usr/share/cups/model/
Once there, you run the script to install it.
I've left the scripts in the Public/Techy Stuff for each printer we use in the highschool.
So, the command looks like this. It's a bit of a trick cause figuring out the details as to how it's supposed to work just by looking in the man pages usually *****.
I'll explain... The command is as follows:
lpadmin -p LabLaser -E -v socket://192.168.1.11 -m HP\ LaserJet\ 1320\ Series.gz -o printer-is-shared=false
lpadmin -p LabLaser adds the printer and calls it "LabLaser"
-E forces encryption while connecting to the server. It's probably not necessary but it's in all the examples on the web that I could find.
-v gives you the opportunity to specify the location of the printer. In ***** case they're all network printers with valid IP addresses and MDNS addresses, so yeah. socket:// for standard IP printing protocol (IPP) mdns:// for bonjour.
Get the mdns name from lpinfo -m
...the -m specifies the name of the PPD. See above. (this is the driver that I copied to /usr/share/cups/model/)
-o is pretty self explanitory... However I feels it's extremely important. This will prevent the printer from showing up in the bonjour list of printers on the network even if the user has printer sharing turned on.
Hope this helps!
-Graham

Airtunes on different subnets - Why not?

I've been googling for the past week in order to try and find out if it is possible to use airtunes on different subnets before I actually buy the device only to find out that it does not satisfy my needs. For various reasons I can not have all my machines into the same subnet.
Searching revealed that because the Airtunes relies on Bonjour which in turn relies onto mDNS (i.e. mullticast) it simply can not be used in two different subnets. I've read that it cannot be done everywhere. I just can't understand the actual reason. Being a network engineer for more than 9 years I find it hard to accept that if both local subnets on my 3640 have multicast routing enabled it still won't do the trick. Can anyone shed some light into this? Unfortunately I still don't own the device so I can not do any tests...
Any help would be much appreciated.
TIA,
GrSpider
Powermac G5 Quad, MB C2D Mac OS X (10.4.9)

GrSpider -
Bonjour (and mDNS) work perfectly well across multiple subnets so long as your router is configured to support (i.e. route) multicast traffic. I use Bonjour on a constant basis across three subnets with both Mac and Windows platforms for a variety of service location purposes (printing, file sharing, streaming media) and have no problems whatsoever.
The AirTunes limitation you're referring to is an Apple policy decision, not a technical issue. It appears they've restricted iTunes<-->Airport streaming media connectivity to connections that originate and terminate on the same subnet. I assume they feel it's a mechanism to help enforce digital rights management.
Just to summarize: I routinely print to my Airport Express units across subnets, and share my iTunes music library to non-AirPort devices on different subnets; I just don't (can't) share my iTunes music library to an Airport Express on a different subnet.
That one limitation aside, they've been a great addition to my network.
FWIW.

SA540, 2.1.18 and mDNS

Similar Messages

Maybe you are looking for