• MCP 60, Software Series. Outgoing TCPIP Connections.

    From Pete Mullins@21:1/5 to All on Sat Aug 22 02:46:39 2020
    Are they blocked by default?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Pete Mullins@21:1/5 to Pete Mullins on Mon Aug 24 04:01:09 2020
    On Saturday, 22 August 2020 at 10:46:40 UTC+1, Pete Mullins wrote:
    Are they blocked by default?

    PS. I am using the port file interface to open a connection to a Windows server application. It worked fine on previous MCPs, but with 60 it just times out. Is the firewall enabled by default and blocking outgoing connections?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Kimpel@21:1/5 to Pete Mullins on Mon Aug 24 15:55:51 2020
    On 8/24/2020 4:01 AM, Pete Mullins wrote:
    On Saturday, 22 August 2020 at 10:46:40 UTC+1, Pete Mullins wrote:
    Are they blocked by default?

    PS. I am using the port file interface to open a connection to a Windows server application. It worked fine on previous MCPs, but with 60 it just times out. Is the firewall enabled by default and blocking outgoing connections?


    Can you ping that Windows server from the MCP?

    I don't have any experience with SSR 60 (MCP 19), so can't speak to
    that. Did this problem occur when you moved to the CSS platform or when
    you upgraded that CSS platform to 60?

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Pete Mullins@21:1/5 to Paul Kimpel on Wed Aug 26 04:14:32 2020
    On Monday, 24 August 2020 at 23:55:54 UTC+1, Paul Kimpel wrote:
    On 8/24/2020 4:01 AM, Pete Mullins wrote:
    On Saturday, 22 August 2020 at 10:46:40 UTC+1, Pete Mullins wrote:
    Are they blocked by default?

    PS. I am using the port file interface to open a connection to a Windows server application. It worked fine on previous MCPs, but with 60 it just times out. Is the firewall enabled by default and blocking outgoing connections?

    Can you ping that Windows server from the MCP?

    I don't have any experience with SSR 60 (MCP 19), so can't speak to
    that. Did this problem occur when you moved to the CSS platform or when
    you upgraded that CSS platform to 60?

    Paul

    Can't ping anything. It was an install. I noticed this:

    nw tcpip identity

    TCPIP IDENTITY

    THIS INTERFACE IS UNAVAILABLE <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
    IPADDRESS 192.168.16.5 / 255.255.255.252
    NP-DEVICE 210, LINEID 0,
    PHYSICAL ADDRESS HEX 000000000000
    AUTOCONFIGURATION FALSE,
    DUPLICATEADDRESSDETECTIONTRANSMITS 1,
    VISIBLE - ,
    DHCP FALSE,
    DNS FALSE,

    THIS INTERFACE IS UNAVAILABLE
    IPADDRESS 192.9.240.108 / 255.255.255.0
    NP-DEVICE 210, LINEID 1,
    PHYSICAL ADDRESS HEX 000000000000
    AUTOCONFIGURATION FALSE,
    DUPLICATEADDRESSDETECTIONTRANSMITS 1,
    VISIBLE + ,
    DHCP FALSE,
    DNS FALSE

    I went back MCP 59, and all ok. Must have screwed up. I'll attempt another install.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Kimpel@21:1/5 to Pete Mullins on Wed Aug 26 07:49:17 2020
    On 8/26/2020 4:14 AM, Pete Mullins wrote:
    On Monday, 24 August 2020 at 23:55:54 UTC+1, Paul Kimpel wrote:
    On 8/24/2020 4:01 AM, Pete Mullins wrote:
    On Saturday, 22 August 2020 at 10:46:40 UTC+1, Pete Mullins wrote:
    Are they blocked by default?

    PS. I am using the port file interface to open a connection to a Windows server application. It worked fine on previous MCPs, but with 60 it just times out. Is the firewall enabled by default and blocking outgoing connections?

    Can you ping that Windows server from the MCP?

    I don't have any experience with SSR 60 (MCP 19), so can't speak to
    that. Did this problem occur when you moved to the CSS platform or when
    you upgraded that CSS platform to 60?

    Paul

    Can't ping anything. It was an install. I noticed this:

    nw tcpip identity

    TCPIP IDENTITY

    THIS INTERFACE IS UNAVAILABLE <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
    IPADDRESS 192.168.16.5 / 255.255.255.252
    NP-DEVICE 210, LINEID 0,
    PHYSICAL ADDRESS HEX 000000000000
    AUTOCONFIGURATION FALSE,
    DUPLICATEADDRESSDETECTIONTRANSMITS 1,
    VISIBLE - ,
    DHCP FALSE,
    DNS FALSE,

    THIS INTERFACE IS UNAVAILABLE
    IPADDRESS 192.9.240.108 / 255.255.255.0
    NP-DEVICE 210, LINEID 1,
    PHYSICAL ADDRESS HEX 000000000000
    AUTOCONFIGURATION FALSE,
    DUPLICATEADDRESSDETECTIONTRANSMITS 1,
    VISIBLE + ,
    DHCP FALSE,
    DNS FALSE

    I went back MCP 59, and all ok. Must have screwed up. I'll attempt another install.


    That display suggests to me that the network interfaces either are not
    enabled in the PCD or that they do not match the CNS and TCPIP INIT files.

    If your 60 install included the firmware for the new TCPv3, the PCD and
    INIT file setup is somewhat different than in the past. I would check
    that out. There is a manual for TCPv3.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)