Author Topic: Getting Unable To Connect to ARSSOCKD Started Task  (Read 454 times)

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1213
    • View Profile
Getting Unable To Connect to ARSSOCKD Started Task
« on: June 13, 2024, 09:30:01 AM »
When getting unable to connect network support is quick to blame CMOD for the issue

Try this before contacting Level 2:

1. Ping the arssockd server host from Windows.  Does that work?

2. Next try the port:

Powershell - (failure shown first, then I opened up the firewall and retried successfully)

PS C:\Users\ed.arnold> test-netconnection 10.1.203.52 -port 1447
WARNING: TCP connect to (10.1.203.52 : 1447) failed
WARNING: Ping to 10.1.203.52 failed with status: TimedOut


ComputerName           : 10.1.203.52
RemoteAddress          : 10.1.203.52
RemotePort             : 1447
InterfaceAlias         : Wi-Fi
SourceAddress          : 192.168.1.133
PingSucceeded          : False
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded       : False



PS C:\Users\ed.arnold> test-netconnection 10.1.203.52 -port 1447


ComputerName     : 10.1.203.52
RemoteAddress    : 10.1.203.52
RemotePort       : 1447
InterfaceAlias   : Ethernet 2
SourceAddress    : 10.111.105.47
TcpTestSucceeded : True


3. If either of these fail it's time for a packet trace to see where the packets are going or not going

4. If all of these are successful then it's time to contact CMOD Level 2

Ed
#zOS #ODF