Advertisement

07.17.2007 at 11:08AM PDT, ID: 22702209
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
7.6

Sonicwall help

Asked by edvernier in Networking Hardware Firewalls, Virtual Private Networking (VPN)

Tags: , ,

We have a VPN setup from IBM to our company, IBM said there is a problem on our side with our Sonicwall TZ-170 with Telnet and file transfer.

Here's what IBM gets

WE ARE ABLE TO PING

$ ping 172.24.26.1

PING 172.24.26.1: (172.24.26.1): 56 data bytes

64 bytes from 172.24.26.1: icmp_seq=0 ttl=62 time=47 ms

64 bytes from 172.24.26.1: icmp_seq=1 ttl=62 time=47 ms

^?64 bytes from 172.24.26.1: icmp_seq=2 ttl=62 time=47 ms

^C

----172.24.26.1 PING Statistics----

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 47/47/47 ms

 

WE ARE NOT ABLE TO TELNET

$ telnet 172.24.26.1

Trying...

telnet: connect: A remote host refused an attempted connect operation.

 

WE ARE NOT ABLE TO SEND A FILE FROM HOST TO THEM VIA THE LAN2LAN

$ cd /usr/pdx/bycom

$ tail -f T2.log

Byque T2 Jul  6 12:49:47 - [2759729] - Site 'TESTMIKE' connecting to host '172.2

4.26.1'

Byque T2 Jul  6 12:49:47 - TCP/IP connection pending

Byque T2 Jul  6 12:49:47 - TCP/IP connect: host='172.24.26.1', IP address='172.2

4.26.1'

Byque T2 Jul  6 12:49:47 -              service='pdxbatch', port='5500'

Byque T2 Jul  6 12:49:47 - connect failed, errno=79: Connection refused

Byque T2 Jul  6 12:49:47 - [2759729] - Job failed - will retry later

Byque T2 Jul  6 12:49:47 - [2759729] - Site 'TESTMIKE' placed on hold

Byque T2 Jul  6 12:49:47 - [2759729] - END-OF-JOB '/usr/pdx/bycom/jobs'

Byque T2 Jul  6 12:49:48 - [2759731] - This site is HOLDING, si 2759729

IBM said Seems like permissions / routing for incoming data is not correct.
Can someone please tell me what changes I need to make on our Sonicwall TZ-170 to make the Telnet and file transfer work for IBM.

Thanks

EDStart Free Trial
[+][-]07.23.2007 at 05:06PM PDT, ID: 19552529

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Networking Hardware Firewalls, Virtual Private Networking (VPN)
Tags: sonicwall, able, refused
Sign Up Now!
Solution Provided By: kinetik20
Participating Experts: 1
Solution Grade: B
 
 
 
Loading Advertisement...
20080716-EE-VQP-32