Using LCS interface and getting TCP error 10061

View: New views
9 Messages — Rating Filter:   Alert me  

Using LCS interface and getting TCP error 10061

by Thomas Dunlap :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I am trying to use TN3270 software (Tom Brennan's Vista) to connect to
MVS.   I have define an LCS device on E20 with IP 10.1.11.24.  This the
same setup we utilized on our Flexes system without fail.  With Hercules
we seem to get a TCP error 10061, which seems to indicate that the host
has rejected the connection.  I have tried several configurations
without any success.  Any help or thoughts would be greatly appreciated.
 
This is Hercules 3.06 running under SLES 11.  Also, I have configured
the two NICs, one with and IP of 10.1.11.21 and the other with
10.1.11.24.  I have even reversed these between the two adapters with
the same results.
 
Cheers,
Tom Dunlap
 
 

RE: Using LCS interface and getting TCP error 10061

by Rocky-11 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Can you send the first 60 or so lines from the LOG as Hercules comes up.

Also the relevant lines from the configuration file.

 

Also your network configuration and Ip addresses.

 

Subnet mask - gateway address - host computer address and guest operating
system address

 

Finally - The beginroute section from the TCPIP configuration

 

Roc

 

  _____  

From: hercules-390@... [mailto:hercules-390@...] On
Behalf Of Thomas Dunlap
Sent: Wednesday, November 11, 2009 14:18
To: hercules-390@...
Subject: [hercules-390] Using LCS interface and getting TCP error 10061

 

 

I am trying to use TN3270 software (Tom Brennan's Vista) to connect to
MVS. I have define an LCS device on E20 with IP 10.1.11.24. This the
same setup we utilized on our Flexes system without fail. With Hercules
we seem to get a TCP error 10061, which seems to indicate that the host
has rejected the connection. I have tried several configurations
without any success. Any help or thoughts would be greatly appreciated.

This is Hercules 3.06 running under SLES 11. Also, I have configured
the two NICs, one with and IP of 10.1.11.21 and the other with
10.1.11.24. I have even reversed these between the two adapters with
the same results.

Cheers,
Tom Dunlap







[Non-text portions of this message have been removed]


Re: Using LCS interface and getting TCP error 10061

by jsganino-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Tom,

    I hate it when that happens.  Conceptually, everything is the same, except for one little thing, but it just won't work.   Alas, I'm afraid were going to have ask a bunch of silly questions to tease out the answer.

1) Is the LCS device defined on a pair of channels, presumably E20 and E21?

2) When your TCPIP is running under MVS under Hercules, does a tun0 device show up in your routing table on the SLES system?

3) Does the TCPIP software come up cleanly under MVS.  (I'm more of a VM person, so I'm used to looking at the console of the TCPIP virtual machine.  I have to believe that all that good information is captured somewhere in MVS.  Maybe SYSPRINT?)

4) Can you ping the MVS machine from the SLES machine?

5) Can you access the MVS machine with an X3270 client from the SLES machine?

If you can let us know, I'll scratch my head a bit and see whether I conjure up some possible things to check.  

Jim

BTW, VISTA is *very* nifty.

--- In hercules-390@..., Thomas Dunlap <thomas.dunlap@...> wrote:

>
> I am trying to use TN3270 software (Tom Brennan's Vista) to connect to
> MVS.   I have define an LCS device on E20 with IP 10.1.11.24.  This the
> same setup we utilized on our Flexes system without fail.  With Hercules
> we seem to get a TCP error 10061, which seems to indicate that the host
> has rejected the connection.  I have tried several configurations
> without any success.  Any help or thoughts would be greatly appreciated.
>  
> This is Hercules 3.06 running under SLES 11.  Also, I have configured
> the two NICs, one with and IP of 10.1.11.21 and the other with
> 10.1.11.24.  I have even reversed these between the two adapters with
> the same results.
>  
> Cheers,
> Tom Dunlap
>



Re: Using LCS interface and getting TCP error 10061

by Thomas Dunlap :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Rocky,

I have attached a "zip" file with 5 TXT files that contain the
information you requested.

The SLES configuration is as follows"
eth0 Firewall disabled MTU 1500 10.1.11.21 mask of 255.255.255.0
eth1 Firewall disabled MTU 1500 10.1.11.24 mask of 255.255.255.0

Cheers,
Tom

Rocky wrote:

>
> Can you send the first 60 or so lines from the LOG as Hercules comes up.
>
> Also the relevant lines from the configuration file.
>
> Also your network configuration and Ip addresses.
>
> Subnet mask - gateway address - host computer address and guest operating
> system address
>
> Finally - The beginroute section from the TCPIP configuration
>
> Roc
>
> _____
>
> From: hercules-390@...
> <mailto:hercules-390%40yahoogroups.com>
> [mailto:hercules-390@...
> <mailto:hercules-390%40yahoogroups.com>] On
> Behalf Of Thomas Dunlap
> Sent: Wednesday, November 11, 2009 14:18
> To: hercules-390@... <mailto:hercules-390%40yahoogroups.com>
> Subject: [hercules-390] Using LCS interface and getting TCP error 10061
>
> I am trying to use TN3270 software (Tom Brennan's Vista) to connect to
> MVS. I have define an LCS device on E20 with IP 10.1.11.24. This the
> same setup we utilized on our Flexes system without fail. With Hercules
> we seem to get a TCP error 10061, which seems to indicate that the host
> has rejected the connection. I have tried several configurations
> without any success. Any help or thoughts would be greatly appreciated.
>
> This is Hercules 3.06 running under SLES 11. Also, I have configured
> the two NICs, one with and IP of 10.1.11.21 and the other with
> 10.1.11.24. I have even reversed these between the two adapters with
> the same results.
>
> Cheers,
> Tom Dunlap
>
> [Non-text portions of this message have been removed]
>
>



[Non-text portions of this message have been removed]



------------------------------------

Community email addresses:
  Post message: hercules-390@...
  Subscribe:    hercules-390-subscribe@...
  Unsubscribe:  hercules-390-unsubscribe@...
  List owner:   hercules-390-owner@...

Files and archives at:
  http://groups.yahoo.com/group/hercules-390

Get the latest version of Hercules from:
  http://www.hercules-390.org

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/hercules-390/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/hercules-390/join
    (Yahoo! ID required)

<*> To change settings via email:
    hercules-390-digest@...
    hercules-390-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    hercules-390-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/


Re: Re: Using LCS interface and getting TCP error 10061

by Thomas Dunlap :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Jim,

I have attached a "zip" file with 5 TXT files that contains the
information on my configuration.

The SLES configuration is as follows"
eth0 Firewall disabled MTU 1500 10.1.11.21 mask of 255.255.255.0
eth1 Firewall disabled MTU 1500 10.1.11.24 mask of 255.255.255.0

I can both PING and TRACERT to the two addresses listed above.

I am able to logon to MVS from an X3270 session running under SLES.
There were no errors when I start TCPIP or TN3270 address spaces under
MVS. It seems to be related to trying to connect through either NIC
adapter. I even tried FTP and received an error that the connection was
rejected by remote host.

Cheers,
Tom



jsganino wrote:

>
> Tom,
>
> I hate it when that happens. Conceptually, everything is the same,
> except for one little thing, but it just won't work. Alas, I'm afraid
> were going to have ask a bunch of silly questions to tease out the answer.
>
> 1) Is the LCS device defined on a pair of channels, presumably E20 and
> E21?
>
> 2) When your TCPIP is running under MVS under Hercules, does a tun0
> device show up in your routing table on the SLES system?
>
> 3) Does the TCPIP software come up cleanly under MVS. (I'm more of a
> VM person, so I'm used to looking at the console of the TCPIP virtual
> machine. I have to believe that all that good information is captured
> somewhere in MVS. Maybe SYSPRINT?)
>
> 4) Can you ping the MVS machine from the SLES machine?
>
> 5) Can you access the MVS machine with an X3270 client from the SLES
> machine?
>
> If you can let us know, I'll scratch my head a bit and see whether I
> conjure up some possible things to check.
>
> Jim
>
> BTW, VISTA is *very* nifty.
>
> --- In hercules-390@...
> <mailto:hercules-390%40yahoogroups.com>, Thomas Dunlap
> <thomas.dunlap@...> wrote:
> >
> > I am trying to use TN3270 software (Tom Brennan's Vista) to connect to
> > MVS. I have define an LCS device on E20 with IP 10.1.11.24. This the
> > same setup we utilized on our Flexes system without fail. With Hercules
> > we seem to get a TCP error 10061, which seems to indicate that the host
> > has rejected the connection. I have tried several configurations
> > without any success. Any help or thoughts would be greatly appreciated.
> >
> > This is Hercules 3.06 running under SLES 11. Also, I have configured
> > the two NICs, one with and IP of 10.1.11.21 and the other with
> > 10.1.11.24. I have even reversed these between the two adapters with
> > the same results.
> >
> > Cheers,
> > Tom Dunlap
> >
>
>



[Non-text portions of this message have been removed]



------------------------------------

Community email addresses:
  Post message: hercules-390@...
  Subscribe:    hercules-390-subscribe@...
  Unsubscribe:  hercules-390-unsubscribe@...
  List owner:   hercules-390-owner@...

Files and archives at:
  http://groups.yahoo.com/group/hercules-390

Get the latest version of Hercules from:
  http://www.hercules-390.org

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/hercules-390/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/hercules-390/join
    (Yahoo! ID required)

<*> To change settings via email:
    hercules-390-digest@...
    hercules-390-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    hercules-390-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/


RE: Re: Using LCS interface and getting TCP error 10061

by fish-8 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thomas Dunlap wrote:

[...]
> I have attached a "zip" file with 5 TXT files that contains
> the information on my configuration. [...]


FYI: this group does not allow file attachments.


Instead, upload your file(s) to the group's "Files" area:


  http://tech.groups.yahoo.com/group/hercules-390/files/


and then post a message with the filename you used.


- --
"Fish" (David B. Trout) - fish@...
Fight Spam! Join CAUCE! <http://www.cauce.org/>
7 reasons why HTML email is a bad thing
http://www.georgedillon.com/web/html_email_is_evil.shtml
PGP key fingerprints:
DH/DSS: 9F9B BAB0 BA7F C458 1A89 FE26 48F5 D7F4 C4EE 3E2A
RSA: 6B37 7110 7201 9917 9B0D 99E3 55DB 5D58 FADE 4A52





-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.8.0 (Build 2158)
Charset: us-ascii

wj8DBQFK+4foSPXX9MTuPioRAgL4AJ9rrw+SlM5DyB4UyeeI2nihuPiVrQCgy0z7
8rqZnt7D/urrBdy8WlnhSf8=
=KPAP
-----END PGP SIGNATURE-----

Re: Using LCS interface and getting TCP error 10061

by jsganino-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Tom,

   Hmmm...  SLES has both devices, eth0 and eth1, defined to it at 10.1.11.21 and 10.11.1.24, respectively, and your MVS has 10.1.11.24 defined to it, too?   My first guess is that you need to enable proxy_arp and give your MVS a different IP address.  There may be a way to dedicate one of the NIC's to Hercules, but I have to toss that one out to the group.  But, if SLES is reporting both NICs and is reporting an IP address for each, that pretty much has to mean that SLES has both and Hercules has none.

   Your zip file didn't make it (Fish explained why in an earlier post), so I'm working blind here, but I will hazard the following offering:

1) Change the IP address on the TCPIP under MVS to something new, like 10.1.11.25.

2) Verify you can still ping and X3270 to MVS at the new address

3) Enable proxy_arp on one (or both) NIC's:
sysctl -w net.ipv4.conf.eth0.proxy_arp=1
sysctl -w net.ipv4.conf.eth1.proxy_arp=1

4) Then try VISTA from across the wire to MVS.

Good Luck,

Jim

--- In hercules-390@..., Thomas Dunlap <thomas.dunlap@...> wrote:

>
> Jim,
>
> I have attached a "zip" file with 5 TXT files that contains the
> information on my configuration.
>
> The SLES configuration is as follows"
> eth0 Firewall disabled MTU 1500 10.1.11.21 mask of 255.255.255.0
> eth1 Firewall disabled MTU 1500 10.1.11.24 mask of 255.255.255.0
>
> I can both PING and TRACERT to the two addresses listed above.
>
> I am able to logon to MVS from an X3270 session running under SLES.
> There were no errors when I start TCPIP or TN3270 address spaces under
> MVS. It seems to be related to trying to connect through either NIC
> adapter. I even tried FTP and received an error that the connection was
> rejected by remote host.
>
> Cheers,
> Tom
>



RE: Re: Using LCS interface and getting TCP error 10061

by Rocky-11 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Suggest you get the Mainframe parameters correct first - since you can ping,

Only after that and it still doesn't work you can move on to the LCS.

 

But for starters - remove the extra device in the configuration,

 

 

 

PROFILE.tcpip

---------------

 

IN ZOS you don't put the telnet parms is the TCPIP profile but in the
TN3270 Profile. You should be getting a message about that.

 

Remove the section telnet parms.

Remove the gateway parms and the default net parms and use the following:

 

BEGINROUTES                                        

ROUTE 10.1.11 255.255.255.0 = ETH1 MTU 1492 (that's your local lan)    

ROUTE DEFAULT 10.1.11.11 ETH1 MTU 1492  (that's your gateway to theworld)


ENDROUTES  

 

In the reserved ports section you are reserving port 23 for a server called
TN3270

 

Is the job are you starting TN3270 or TN3270A?

Name and port  that you reserve must match the job you submit

 

So check the startup to see that you are starting the proper procedure

 

 

 

In the TN3270 Configuration you have some errors.

Not sure how critical that is But I modifies yours parameter file and it now
looks like this.

try it.

 

TelnetGlobals                                                    

  INACTIVE 28800                                                

  SMFINIT STD                                                    

  SMFTERM STD                                                    

  TIMEMARK 14400       ; NO IP ACTIVITY FOR 4 HOURS, SEND TIMEMAR

  LUSESSIONPEND                                                  

  ScanInterval 3600    ; Check for IP activity every 1 hour      

  MAXRECEIVE  65535                                              

  MAXVTAMSENDQ 50                                                

  TCPIPJOBNAME TCPIP                                            

  ; ----------------------------------------


  TELNETDEVICE 3278-2-E NSX32702 ; 24 line screen -              

  TELNETDEVICE 3279-2-E NSX32702 ; 24 line screen -              

  TELNETDEVICE 3278-3-E NSX32703 ; 32 line screen -              

  TELNETDEVICE 3279-3-E NSX32703 ; 32 line screen -              

  TELNETDEVICE 3278-4-E NSX32704 ; 48 line screen -              

  TELNETDEVICE 3279-4-E NSX32704 ; 48 line screen -              

  TELNETDEVICE 3278-5-E NSX32705 ; 132 column screen-            

  TELNETDEVICE 3279-5-E NSX32705 ; 132 column screen -          

                                                                 

EndTelnetGlobals                                                

 

***** pay attention to the WLM parameter --- same name as the reserved in
the port

 

; ---------------------------------------------------------------------

; Required Port Configuration affects the specified port                

; ---------------------------------------------------------------------

                                                                       

TelnetParms            ; Standard TN3270 Telnet server port            

  Port 23                                                              

    WLMClusterName     ; Define WLM name for this port                  

      TN3270           ;         Must have JOBNAME coded to use WLM        

    EndWLMClusterName                                                  

EndTelnetParms                                                          

                                                                       

BeginVTAM              ; Mapping for basic and TTLS ports.              

 Port 23;                                                            

 DEFAULTLUS           ; Define LUs to be used for general users.      

   SC0TCP01..SC0TCP30                                                  

 ENDDEFAULTLUS                                                        

 LUGROUP EVERYONE                                                      

    SC0TCP01..SC0TCP30                                                

 ENDLUGROUP                                                            

 LINEMODEAPPL TSO     ; Send all line-mode terminals directly to TSO.  

 ALLOWAPPL TSO* DISCONNECTABLE                                        

                      ; Allow all users access to TSO applications.    

                      ; TSO uses unique applications for each session  

                      ; which all begin with TSO.  Use TSO* to cover  

                      ; all TSO sessions.                              

                      ; If a session is closed, disconnect the user    

                      ; rather than log off the user.                  

 ALLOWAPPL *          ; Allow access to all applications.              

 USSTCP USSN          ; Send out the default TN USS table              

 LUMAP EVERYONE KEEPOPEN                                              

                                                                       

 EndVTAM                                                              

             

                                                   

Rocky

 

 

 

 

 

 

  _____  

From: hercules-390@... [mailto:hercules-390@...] On
Behalf Of jsganino
Sent: Thursday, November 12, 2009 18:19
To: hercules-390@...
Subject: [hercules-390] Re: Using LCS interface and getting TCP error 10061

 

 

Tom,

Hmmm... SLES has both devices, eth0 and eth1, defined to it at 10.1.11.21
and 10.11.1.24, respectively, and your MVS has 10.1.11.24 defined to it,
too? My first guess is that you need to enable proxy_arp and give your MVS a
different IP address. There may be a way to dedicate one of the NIC's to
Hercules, but I have to toss that one out to the group. But, if SLES is
reporting both NICs and is reporting an IP address for each, that pretty
much has to mean that SLES has both and Hercules has none.

Your zip file didn't make it (Fish explained why in an earlier post), so I'm
working blind here, but I will hazard the following offering:

1) Change the IP address on the TCPIP under MVS to something new, like
10.1.11.25.

2) Verify you can still ping and X3270 to MVS at the new address

3) Enable proxy_arp on one (or both) NIC's:
sysctl -w net.ipv4.conf.eth0.proxy_arp=1
sysctl -w net.ipv4.conf.eth1.proxy_arp=1

4) Then try VISTA from across the wire to MVS.

Good Luck,

Jim

--- In hercules-390@ <mailto:hercules-390%40yahoogroups.com>
yahoogroups.com, Thomas Dunlap <thomas.dunlap@...> wrote:

>
> Jim,
>
> I have attached a "zip" file with 5 TXT files that contains the
> information on my configuration.
>
> The SLES configuration is as follows"
> eth0 Firewall disabled MTU 1500 10.1.11.21 mask of 255.255.255.0
> eth1 Firewall disabled MTU 1500 10.1.11.24 mask of 255.255.255.0
>
> I can both PING and TRACERT to the two addresses listed above.
>
> I am able to logon to MVS from an X3270 session running under SLES.
> There were no errors when I start TCPIP or TN3270 address spaces under
> MVS. It seems to be related to trying to connect through either NIC
> adapter. I even tried FTP and received an error that the connection was
> rejected by remote host.
>
> Cheers,
> Tom
>





[Non-text portions of this message have been removed]


Re: Using LCS interface and getting TCP error 10061

by Rocky-11 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Whoops small typo in the begion route section

should be 10.1.11.1   which I believe is the gatway on your lan or your internet router

--- In hercules-390@..., "Rocky" <rocsystems@...> wrote:

>
>  
>
>  
>
>
>  
>
> BEGINROUTES                                        
>
> ROUTE 10.1.11 255.255.255.0 = ETH1 MTU 1492 (that's your local lan)    
>
> ROUTE DEFAULT 10.1.11.11 ETH1 MTU 1492  (that's your gateway to theworld)
>
>
> ENDROUTES  
>
>  
>
>