SADTP1/SADTT1 ACCESS SETUP AND TROUBLSHOOTING STEPS
SADTP1 and SADTT1 are two Windows 2008 servers used for transferring files in and out of our enterprise
application environments. SADTP1 is production and SADTT1 is test. ESA manages these boxes.

Requests for ADS group additions and their corresponding new directories need to come from a
technical manager (Julie Parmenter, Sandy Thompson, and Randall Embry) and be submitted via
the SADTP1/SADTT1 ADS Group Request form
https://www.iu.edu/~asateam/sadtxx_forms/pssadtads_form.php.

Requests for adding users to new or existing ads groups and requesting that their static IP be
added to the SADT server filter must come from a technical manager (Julie Parmenter, Sandy
Thompson, and Randall Embry) and be submitted via the SADTP1/SADTT1 Access Request form
https://www.iu.edu/~asateam/sadtxx_forms/pssadtuser_form.php.
o A static IP or connecting to your team’s SSL VPN is required to access SADTP1 and
SADTT1 because of the filter list. Your LSP can request a static IP for you, or if you have
no LSP, you can request a static IP via this IU KB article
o
Use IU’s naming convention (e.g. bl-uits-xxx-xxx)
http://kb.iu.edu/data/atjq.html.
o
The static IP must have a forward and reverse DNS lookup in order for SSH to work.
 NOTE that the static IP will need proper DNS setup for the connections
to SADTP1/SADTT1 to work correctly. The machine name for both DNS
records must match. These two KB articles describe how to get it setup
for Windows workstations.
http://kb.iu.edu/data/akir.html
http://kb.iu.edu/data/akne.html

After the IP has been added to the filter, if a user still has problems accessing the server, this
usually means that their IP address does not have a proper PTR record or they are not using the
correct protocol to connect to the servers.
o Perform an nslookup command on the IP address and then also the machine name to
make sure they match
 Open a command prompt and type nslookup computer name and then press
enter. This should reveal the static IP of the computer. Then, do the nslookup
computer IP and press enter. This should reveal the name of the computer. If
this doesn’t happen, then email your LSP with your computer name and static IP
and ask them to contact dns-admin and fix your dns entry.
o You can only access SADTP1 and SADTT1 using a file transfer protocol (scp/sftp)


Window Users: WINSCP http://kb.iu.edu/data/ahjh.html and config instructions:
connect via sftp (file transfer session) ONLY
MAC Users: Cyberduck on IUWARE and config instructions:
http://kb.iu.edu/data/akom.html
o
NOTE: If you still can’t figure it out, ask the ESA team to check their logs to see if they
can see why you can’t access the server.
Steps and responsibility areas for setting up access to SADTP1/SADTT1
Note: SADTP1 and SADTT1 are two Windows 2008 servers used for transferring files in and out of our
enterprise application environments. SADTP1 is production and SADTT1 is test. ESA manages these
boxes.
1. Technical Managers submit an SADTP1/SADTT1 ADS Group Request form
https://www.iu.edu/~asateam/sadtxx_forms/pssadtads_form.php for ADS group(s) with a request
to add a directory/directories on SADTP1/SADTT1. *Request separate groups for PRD and TST.
Use IU’s naming convention (e.g. bl-uits-xxx-xxx)
a. ESA requires global groups be created
2. Technical Managers request (via the SADTP1/SADTT1 Access Request form
https://www.iu.edu/~asateam/sadtxx_forms/pssadtuser_form.php) the addition of usernames to
the ADS group, and the corresponding IPs to be added to the filter.
3. ASA creates the ADS group(s).
4. ASA adds names to ADS groups, and requests from ESA that the IPs be added to the filter.
5. User\Developer must access SADTP1/SADTT1 via SSH2 client.
a. Window Users: WINSCP and Putty http://kb.iu.edu/data/ahjh.html and config instructions:
connect via sftp (file transfer session) ONLY
b. MAC Users: Cyberduck on IUWARE and config instructions:
http://kb.iu.edu/data/akom.html
NO TERMINAL SESSIONS ALLOWED only FILE TRANSFER SESSIONS ARE ALLOWED