Skip to main content
Created On:  05 December 2012

Problem:

There appears to be a change since Rumba 8.1 where when you type in "localhost" to connect to your mainframe it shows a windows socket error 10061 and the connection fails. But when you type in 127.0.0.1 it works fine.

Resolution:

When you type "ping -a localhost", what address is returned by the IP stack?  Is it ::1?

Rumba 8.2 is IPv6 aware now.  So what is happening is that Rumba is asking the stack to resolve "localhost", and it's returning "::1", the IPv6 loopback address.  Rumba attempts to connect to that address, but the Server application is only bound to the IPv4 address, so there is no response to the connect attempt.  If you look in your hosts file (Windows\\System32\\Drivers\\etc\\hosts), there is a commented entry for both localhost types there:

 

#             127.0.0.1              localhost

#             ::1                           localhost

 

If you uncomment the 127.0.0.1 entry, it works.

Old KB# 36663

#Rumba
Created On:  05 December 2012

Problem:

There appears to be a change since Rumba 8.1 where when you type in "localhost" to connect to your mainframe it shows a windows socket error 10061 and the connection fails. But when you type in 127.0.0.1 it works fine.

Resolution:

When you type "ping -a localhost", what address is returned by the IP stack?  Is it ::1?

Rumba 8.2 is IPv6 aware now.  So what is happening is that Rumba is asking the stack to resolve "localhost", and it's returning "::1", the IPv6 loopback address.  Rumba attempts to connect to that address, but the Server application is only bound to the IPv4 address, so there is no response to the connect attempt.  If you look in your hosts file (Windows\\System32\\Drivers\\etc\\hosts), there is a commented entry for both localhost types there:

 

#             127.0.0.1              localhost

#             ::1                           localhost

 

If you uncomment the 127.0.0.1 entry, it works.

Old KB# 36663

#Rumba

I'm not sure why this is under RM/COBOL. It's primarily relevant to Enterprise Server, which is what Rumba is likely connecting to, if you're asking it to connect to localhost.

Another workaround is to configure Rumba to connect to "127.0.0.1" rather than "localhost".