Hi,

Many thanx for your quick responses, it really is much appreciated :-)

We were just about to re-run the wizard as you both suggeseted, but
then took a long shot which did kinda work as a temp solution.

We added another IP on the first NIC then in IIS hosted the default
website on that IP.  will obviously need to fix it properly soon.

I hope you dont mind if i ask a few more questions:

1)Being that hosting the site on the original IP is now forbidden,
this would indicate a rule or permission in the ISA blocking web
traffic to that IP!! Is this Correct???

2)I know very little about ISA, now in a basic network that at present
only uses POP to get mail SMTP to send it and all internal clients use
outlook 2000 exchnage clients and port 8080 to access net through the
proxy, I feel there may be far to many rules and filters in the ISA.
Do you know of any good straight forward sources that could aid a
better config??? firewall is bit lax at mo (I know it sounds terribly
general,so sorry!)

Now being that you ask about the initial SSL problem i'll fill you in.
Now until now no network PC's have had any problem accessing any web
sites including SSL sites.  recently the customer needs to use the
following site www.woolworths.co.uk/supplier/somi.  This site is
accessible however the moment you try to log in the site just seems to
freez and the IE globe just keeps spinning.  Once in a blue moon it
does get through and then just freezez on the very next part of the
site.  When ISA is disabled it works fine.

Spoke to woolworths and because we can access the customer purchase
part of the site they can't understand why as it has supposedly used
all the same web components etc. eventhough they admit they have not
spent anywhere near as much time optimizing the supplier site.

Thinking about it now, it may not even really be an SSL problem but
could be.

If you do have any ideas or thoughts i really would be most greatful.