Date: Wed, 20 Dec 2000 11:50:58 -0600 From: "Evoniuk, Rodney" <Rodney.Evoniuk@westgroup.com> To: "'freebsd-questions@freebsd.org'" <freebsd-questions@freebsd.org> Subject: FW: BSD Proxy not responding to a script (32 bit version of our s oftware) Message-ID: <27CD34D68C7DD211A68A0004AC38272A03E27F76@elizabeth.int.westgroup.com>
next in thread | raw e-mail | index | archive | help
Sorry I just realized in my original email I forgot to give you the version of the Free BSD on the telnet session it says "FreeBSD 2.2.8-RELEASE (GENERIC)#0:" > -----Original Message----- > From: Evoniuk, Rodney > Sent: Monday, December 18, 2000 12:48 PM > To: 'freebsd-questions@freebsd.org' > Subject: BSD Proxy > > I am a network specialist supporting our products in a network > environment. > Our software uses telnet access from the local machine to access our > servers here. The issue I have been encountering with a client, who > states > they are using a Unix BSD Application Proxy on their network, is that I > can > utilize telnet itself to get to our threshold. But, when I attempt to > script this into our software application it appears like I cannot get > their proxy/firewall to respond. I have spent days working with the > client > checking all angles of our software and our script to get through the > firewall, and by all means given the telnet session it should pass through > this proxy server, but it will not respond to any portion of our script. > I > have even sent a telnet details command, within a script, looking for any > response from the proxy but the proxy returns no response. > > > The telnet port the customer is using is 23, terminal type is VT100. > > I have enclosed a link to our software download it can be installed > locally for test purposes the link is: > > http://software.westgroup.com/esd/software/WM73Win/dlinstr.asp?first_name= > rodney&last_name=Evoniuk&city=Egan+&state=MN&country=&email=rodney.evoniuk > @westgroup.com&phone=123-456-7888&bnSubmit=Continue > > > Once installed launch the software and choose cancel at the sign on > screen. To setup the firewall script mentioned above you go to tools, > communication options and click on the advanced access tab. Then click on > Scripts and first choose westsock then click on properties, you will see > the following script: > > 10 label 'Internet // Windows Sockets' > 20 genmsg > 30 versions > 40 getport > ;45 firewall > 50 on 'fail',150 > 60 <serviceScript> > 70 on 'fail',150 > 80 goto 180 > 150 ems 'Access failed. Please try again.' > 170 end > 180 exit > > > Unrem line 45 (take out the ";") and save > > then choose firewall from the script list and you will see the following > script: > > 25 lfstatus 'Connected to firewall.' > ;27 prompt 'Username:', login_code > ;28 prompt 'Password:', password, 1 > 30 rx 'login:', 80 > 40 pause 150 > 50 lfstatus 'Login prompt not received from firewall.' > 60 return 'fail' > 80 tx '<login>',<delay> > 85 tx '^M',<delay> > 90 rx 'password:',140 > 100 pause 150 > 110 lfstatus 'Password prompt not received from firewall.' > 120 return 'fail' > 140 tx '<password>',<delay> > 145 tx '^M',<delay> > 150 rx '$', 200 > 160 pause 150 > 170 lfstatus '$ prompt not received from firewall.' > 180 return 'fail' > 200 tx 'telnet westlaw.westlaw.com',<delay> > 210 tx '^M',<delay> > 500 end > > > the changes we typically make are as follows: > > 30 rx ':',80 > 80 tx 'enter your login here for firewall',<delay> > 90 rx ':' ,140 > 140 tx 'enter your password her for firewall' <delay> > 150 rx '>',200 > > NOTE: these are dependant on a telnet session for example: > > AIX Version 4 > (C) Copyrights by IBM and by others 1982, 1996. > login: ************** > ***********'s Password:*********** > ************************************************************************** > ***** > * > * > * > * > * Welcome to AIX Version 4.2! > * > * > * > * > * > * Please see the README file in /usr/lpp/bos for information pertinent to > * > * this release of the AIX Operating System. > * > * > * > * > * > ************************************************************************** > ***** > Last login: Tue Dec 12 11:02:36 2000 on /dev/pts/0 from *****(our proxy > address)***** > > $ > > given this telnet session I would use the following changes: > > 30 rx ':',80 > 80 tx '************',<delay> > 90 rx ':' ,140 > 140 tx '************' <delay> > 150 rx '$',200 > > ONE Last change must be done before you can attempt to sign on using our > software is to go to the General TAB in the communications setup and make > sure the communication device is TCP/IP the remote IP address is the > address of your firewall and the sign on option tab (on the left hand > side) is set to Westlaw via Windows Sockets > > > given this scenario the client I refer to does not get the first rx from > the firewall i.e. line 30 even if we set our software to show details it > fails to do so there appears like using this scripting feature that we get > no response from the firewall. > > NOTE: a person can change the port our script would use for the telnet > and turn on details from the firewall by simply launching the following > file from C:/program files/west Group/Westmate/SysAdmin.exe choose > setup, Registry setup and change the TCP port to the desired telnet port > and to turn on details from the proxy and/or firewall simply type in Yes > instead of the No entered in the Telnet Display box. > > > ONCE the changes are made to the communications as mentioned one should be > able to go to File, Sign on westlaw, It will prompt you for a password: > you can simply enter in 12345abc and you must enter in a client ID you > can type in test and although this will not let you on to Westlaw it > should take you to our door step and give you an error that password is > not valid. But during the signon procedure you can click on the details > tab and it will give you a detailed message of the script and script > errors along with the details from the proxy/firewall if you edited the > SysAdmin.exe file and changed the Telnet Display from NO to Yes. > > > As mentioned we have tried several different changes to the script but no > matter what I do it appears that the firewall is not responding to our > script and we get no details NOTE if you go back into the SysAdmin.exe > file to check your settings they are automatically changed back to the > default settings and it does not reflect your changes. Your changes are > automatically changed in the actual registry for our program... > > > > Thank You for any help you can provide If I can be of service in helping > you set this up for testing please feel free to give me a call at > 1-800-WESTLAW ext. 76818 Also if you need an actual password for > further testing I can provide you with one, but I cannot email you one. > > > Sincerely; > Rodney H. Evoniuk > West Group > Network Specialist > > > PS we do not install proxy servers for clients To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?27CD34D68C7DD211A68A0004AC38272A03E27F76>