I like WSA. Much quicker and faster than PCOMMs.
However, I too am suddenly experiencing problems.
I am using a remote connection to my server via: Cisco Anyconnect->Citrix XenApp->VPN->TPX->TSO! (give me my SNA back!).
The VPN part is flaky enough and often takes multiple PC Restarts to get going!
When I try to start WSA, which I have as a shortcut on my TaskBar (and has worked before many times), it starts OK and displays the WSA popup with
0 session(s) are active.
Then I go to my MS Command Prompt and enter IPCONFIG. (address changed to protect the inocent/guilty
)
C:\Users\n472730>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection* 11:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fc20::715b:f40:d51e:3885%16
IPv4 Address. . . . . . . . . . . : 10.64.8.32
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 10.0.0.1
Ethernet adapter Bluetooth Network Connection:
I Mark & Cut this to the clipboard and Paste it into my WSCON panel. Press ENTER and wait. . . . . . .
Finally...
(Sorry, no GE(ON) ISPF Attributes available here)EsssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssN s
e Initiate Workstation Connection e
e Command ===> e
e More: + e
e / Save values in system profile? (/=Yes) e
e e
e Workstation Connection GUI Network Protocol e
e 2 1. With GUI display 1 1. TCP/IP e
e 2. Without GUI display 2. APPC e
e 3. Use ISPDTPRF file e
e e
e GUI Title e
e e
e TCP/IP Address e
e 10.64.8.32 e
e APPC Address e I
e e 2
EsssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssN
e ISPO921 Unable to communicate with workstation at the specified network e
e address. Probable causes: (1) the specified network address does not e
e exist or cannot be accessed; (2) if specified, the SNA network address e
e does not support APPC communication. Network data:'TCP/IP CONNECT RC=60 e
e '. e
DsssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssM
I also tried this with the "Wireless LAN adapter Wireless Network Connection" IP Address, same result.
Not really expecting a solution here. I will try it at work next week. That should at least omit the (flaky) VPN bit?