This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Mary Ellen, re: > I was thinking I would set up dataloc.k to point to the ingestors IP address > via ADDE > e.g., dataloc.k ADD GER nnn.nn.nnn.nn OK, now I understand that you want your colleagues to be able to access your data via ADDE, not by an LDM transfer. re: > Other than removing the dataloc is there another way to stop access? This is easiest handled by your firewall -- setup the firewall to allow inbound traffic to port 112 (the ADDE port) during the period where you want to allow access by your colleagues, and then change the firewall setup to block their access when you want their access to stop. I am sure that you will have to go through your network folks to allow their access in the first place, so they will know exactly what to remove when you are finished. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: MKS-208085 Department: Support McIDAS Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.