Scheduled import error

[california123]

Hi,

I am getting this error

"java.io.IOException: SSH authentication failed, Failed to connect TCP"

when i tried with scheduled import .

i added both parameters and tried but its not working :   mid.ssh.use_keyboard_interactive and mid.ssh.use_snc=true

I have selected the "SFTP" as the File retrieval method

   

[Dave Smith1]

The first check I can suggest is to use the "Discovery Credentials" module and specify the credentials you are using in there, then use the "Test Credentials" button to verify connectivity.   However, what you are doing does't sound like a normal process, though. Usually people perform one of the following:

• an import from a server
• place requests (in the form of probes) that the MID server will collect as work to do.

.. so this module will actually test if the MID server can communicate with that IP address using those credentials, not if your instance can communicate with the IP.

Your Unix servers may be MID servers, but the import you're attempting isn't using any MID server functionality - is the question "Scheduled Import for importing file from a Unix server on 19.7.26.102" more accurate? It sounds like the MID server part is irrelevant in this case.

Is that IP address (19.7.26.102) accessible from the internet? It seems to be owned by Ford.

[california123]

for some security i modified original IP

can Please tell me how to pull / pick file (xslx / csv ) from mid server to servicenow

[Dave Smith1]

Have you tested to see if that IP and port are accessible to the internet? Your instance needs to connect to it over SSH/SFTP

Also, as I mentioned - you're not really pulling the file from a MIDserver, you're pulling it from a UNIX server. The MID server part is irrelevant in this case.

[california123]

i checked with server team they replied port is opened. you want me do anything other than that check (that IP and port are accessible to the internet)

how to connect / how to configure my instance connect to it over SSH/SFTP

Thanks for your Time.

[Dave Smith1]

Have you tested to see if that IP and port are accessible to the internet? <-- that's the first check you need to do.

SSH into it from another IP outside your firewall, confirm it's reachable. Until there is evidence it's routable and accessible, it's pointless adding details to your instance.