ctsuhako
asked on
ISeries and Client Access Issue
Hello:
I am hoping someone can help me an issue I am having at work trying to connect via
IBM's Client Accces (Version 5.9 for Windows) to a remote iSeries server. Here is
the issue:
We currently connect to a remote iSeries server using Client Access without any
problems. However, this server is due to be retired and will be replaced with a
new server. The remote, public IP address will change but it will still be in the
same range (72.xxx.xxx.251 is the IP of the new server, old server is
72.xxx.xxx.249). The new server is currently up and running but I am unable to
connect to it. When I go to verify the connection in System i Navigator I get the
following errors:
Attempting to establish connection
CWBC01003-Sockets error, function connect() returned 10060
CWBC01048-A firewall blockage or time-out occurred trying to connect to the System
i
CWBC01006-Unable to connect to server mapper
CWBC01011-Remote port could not be resolved
CWBC01008-Unable to connect to server application Central Client, returned 10060
These errors repeat for all the various types of connections Client Access is
trying to establish. Verififcation on the old server works just fine.
My first troubleshooting attempt was to try to connect from outside our network to
make sure there wasn't an issue on the iSeries itself. I was able to connect
without a problem from both home and from my IPad using a cellular connection.I
then looked at our Sonicwall firewall to see if there were any rules blocking the
new IP and found that the IP range (72.xxx.xxx.246 to 72.xxx.xxx.252) is set to
allow all communication and protocols/ports to pass thru in both directions.
The next step I tried was to download and install Mocha TN5250 to see if I could
connect using that. Lo and behold I was able to connect without any problem which
leads me to believe that the issue is with Client Access.
Has anyone seen anything like this before and are there any suggestions on what
steps I should take to try and correct this? Using Mocha is not an option here and
we do need to get Client Access working on the new server.
Thanks very much!
I am hoping someone can help me an issue I am having at work trying to connect via
IBM's Client Accces (Version 5.9 for Windows) to a remote iSeries server. Here is
the issue:
We currently connect to a remote iSeries server using Client Access without any
problems. However, this server is due to be retired and will be replaced with a
new server. The remote, public IP address will change but it will still be in the
same range (72.xxx.xxx.251 is the IP of the new server, old server is
72.xxx.xxx.249). The new server is currently up and running but I am unable to
connect to it. When I go to verify the connection in System i Navigator I get the
following errors:
Attempting to establish connection
CWBC01003-Sockets error, function connect() returned 10060
CWBC01048-A firewall blockage or time-out occurred trying to connect to the System
i
CWBC01006-Unable to connect to server mapper
CWBC01011-Remote port could not be resolved
CWBC01008-Unable to connect to server application Central Client, returned 10060
These errors repeat for all the various types of connections Client Access is
trying to establish. Verififcation on the old server works just fine.
My first troubleshooting attempt was to try to connect from outside our network to
make sure there wasn't an issue on the iSeries itself. I was able to connect
without a problem from both home and from my IPad using a cellular connection.I
then looked at our Sonicwall firewall to see if there were any rules blocking the
new IP and found that the IP range (72.xxx.xxx.246 to 72.xxx.xxx.252) is set to
allow all communication and protocols/ports to pass thru in both directions.
The next step I tried was to download and install Mocha TN5250 to see if I could
connect using that. Lo and behold I was able to connect without any problem which
leads me to believe that the issue is with Client Access.
Has anyone seen anything like this before and are there any suggestions on what
steps I should take to try and correct this? Using Mocha is not an option here and
we do need to get Client Access working on the new server.
Thanks very much!
Sounds like it could be a local PC firewall issue. Are you running Windows Firewall (or anything else) on the problem system that might be interfering? Try temporarily disabling any client firewall programs and see if the problem persists.
ASKER
Hello:
Firewall is off on the PC. Why would the firewall affect Client Access but not Mocha TN5250? Also, othe Client Access sessions work just fine.
Firewall is off on the PC. Why would the firewall affect Client Access but not Mocha TN5250? Also, othe Client Access sessions work just fine.
Client Access does things a little different than Mocha.
For example, Client Access queries the server mapper process to determine what port various services run on. If I recall correctly, Client Access also calls the remote logon service before establishing a TN5250 session - Mocha doesn't.
So if the dependent services aren't visible from that client system, Client Access may be unable to connect where Mocha can.
For example, Client Access queries the server mapper process to determine what port various services run on. If I recall correctly, Client Access also calls the remote logon service before establishing a TN5250 session - Mocha doesn't.
So if the dependent services aren't visible from that client system, Client Access may be unable to connect where Mocha can.
ASKER
Thanks, Gary. What I can't understand is why I can connect from the same machine using Client Access to another iSeries without any problem.
That can be a local firewall issue. Let's eliminate that first.
ASKER
Hi, Gary:
Windows firewall is off on the local pc. In addition, I have removed Symantec Antivirus but still no luck with Client Access to that server.
Windows firewall is off on the local pc. In addition, I have removed Symantec Antivirus but still no luck with Client Access to that server.
Can you test the failing PC from outside your network? i.e. test it from home or DMZ.
This would indicate if problem is on PC or inside network.
This would indicate if problem is on PC or inside network.
ASKER
I don't believe it is limited to this PC since other PCs on the network have the same issue. As I said, we can connect to other ISeries servers using Client Access without a problem. It is just this one ISeries that we are having an issue with. And outside the network I can connect.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
After all this, it turned out that the issue was on the remote iSeries. I thank you all for your help!