Linkpoint Wrapper Port Internal Errors

I have a webserver that is internal using the linkpoint wrapper CFtag
for processing credit card transactions. The tag uses port 1139 to
communicate with the linkpoint secure gateway. My internal web server
won't connect to the linkpoint gateway through port 1139
 
I have made protocol definition for 1139 inbound first then added a
secondary for outbound on the same 1139 I then made a protocol rule for
it to allow I then make a server publishing rule for the protocol
 
The error the CFX tag gives me is :  unable to connect to SSL server.
 
This SSL server is using 1139 to communicate. I have verified that it is
using just this port for in and out after calling linkpoint tech
support.
 
The tag keeps telling me that it cant connect. I know it works when the
server is on the outside but I can't seem to make ISA communicate
correctly with my internal webserver  and the linkpoint servers via port
1139 
 
I even tried to make a web publishing rule for the port as well and no
dice. Every single config I try doesn't work.
 
I have also deleted all of the protocol rules and publishing rules and
recreated them STILL NOTHING.
 
Someone please tell me something cuz I am losing many dollars daily
because I can't process transactions on my friggin site. LAME LAME LAME.

 
Sean

-----Original Message-----
From: Dave Morrow [mailto:David.Morrow@xxxxxxxxxxxx] 
Sent: Friday, November 30, 2001 7:47 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Publishing Exchange Server - Weird Problem

http://www.ISAserver.org


I'll check out that Hotfix.  Thanks for the tip.  
You're right, it does seem to be the Win98 clients that mostly
experience
the problem.  It's strange though, when the client connects to resolve
the
hostname (entered as "exchange.mydomain.com") it successfully connects,
changes the servername to the NETBIOS name and confirms the mailbox
name.
Then, when Outlook tries to actually connect to the mailbox, it fails.
I
tried using the LMHOSTS file and that does cure the problem, but I
really
would rather not place LMHOSTS files on all of my mobile users
laptops....know what I mean?  I wonder if, for some reason after
connecting,
and resolving the mailbox name, if the client is placing the private IP
address of the exchange server in the profile somehow????

-----Original Message-----
From: Iain.Mclaren@xxxxxxxxxxxx [mailto:Iain.Mclaren@xxxxxxxxxxxx] 
Sent: Friday, November 30, 2001 4:41 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Publishing Exchange Server - Weird Problem


http://www.ISAserver.org


This problem may be related to one of a few issues
What version of O/S are the Outlook clients running?
If its anything older than Windows2000 then you will 
need to apply MS Hotfix Q291000 to the ISA server, 
as the RPC connect packets from older MS O/S's (win95 through NT4) don't
comply with ISA server's RPC filter. 
However it could also be that the client isn't able to resolve the 
Netbios name of the exchange server (the server name displayed after a 
check mailbox name in the outlook client completes successfully) a quick
and
easy way to test this is to enable the clients lmhosts file and add an
entry
of the Netbios name of the exchange server being published and the IP
address of the ISA rule publishing it.

Iain



-----Original Message-----
From: Dave Morrow [mailto:David.Morrow@xxxxxxxxxxxx]
Sent: 29 November 2001 16:01
Subject: RE: Publishing Exchange Server - Weird Problem


Actually, I should have been more clear.  The problem exists with an
Exchange Server client using RPC communications

-----Original Message-----
From: Muqeem Syed [mailto:Syed.Muqeem@xxxxxxxxxxxx] 
Sent: Thursday, November 29, 2001 10:54 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Publishing Exchange Server - Weird Problem


http://www.ISAserver.org


the outgoing connection form the server is made to a random port on the
client side.. check to see if you have any outgoing protocol rule that
denies outgoing traffice on certain ports.. .. the incoming traffic to
the
server is on port 25 but outgoing port could be any random port.. you
might
want to check if there is any outgoing protol rule that defines to deny
traffic on those ports. 


-----Original Message-----
From: Dave Morrow [mailto:David.Morrow@xxxxxxxxxxxx]
Sent: Thursday, November 29, 2001 4:40 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] Publishing Exchange Server - Weird Problem


http://www.ISAserver.org


I have this very strange problem with publishing an Exchange server
behind
ISAServer.

I use the "Secure Mail Server" publishing wizard to publish my Exchange
server.  Everything works fine with respect to POP/SMTP but Outlook
clients
connecting to my server can only resolve their mailbox name (when they
setup
their profile).  When they launch Outlook it fails to connect to the
server.
I know it can connect since it properly resolves the name and sets up
the
profile.

David A. Morrow
Network Administrator
Autodata Solutions Company
David.Morrow@xxxxxxxxxxxx
http://www.autodata.net <http://www.autodata.net> 
Phone: (519) 951-6067   Fax: (519) 451-6615

This message has originated from Autodata Solutions Company. The
attached
material is the Confidential and proprietary Information of Autodata
Solutions Company. This email and any files transmitted with it are
confidential and intended solely for the use of the individual or entity
to
whom they are addressed. If you have received this email in error please
delete this message and notify the Autodata system administrator at
ADMINISTRATOR@xxxxxxxxxxxx





------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
syed.muqeem@xxxxxxxxxxxx To unsubscribe send a blank email to


------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
david.morrow@xxxxxxxxxxxx To unsubscribe send a blank email to


********************************************************************

This email may contain information which is privileged or confidential.
If
you are not the intended recipient of this email, please notify the
sender
immediately and delete it without reading, copying, storing, forwarding
or
disclosing its contents to any other person Thank you

Check us out at http://www.syntegra.com

********************************************************************


------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
david.morrow@xxxxxxxxxxxx To unsubscribe send a blank email to
$subst('Email.Unsub')

------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
colter@xxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')

Other related posts: