Tennessee_Pride
asked on
ISA Publich Multiple WEbsites on single External IP address
Hi there..me again. Im trying to publish a second internal website thats hosted on a different internal computer to the same external IP address. I tried adding a differnet listener on a different port, no love. I tried using the same listener as the web published currently that works, nothing.
Is there some trick im missing?
Is there some trick im missing?
ASKER
o ya..Im trying to publish a page in sharepoint. Redirecting an external Vendor to acccess a specific folder.
Hi dude.
So, same external IP address.
Different internal IP address
Both using port 80?
So, same external IP address.
Different internal IP address
Both using port 80?
If its sharepoint, shouldn't be an issue
Create the rule put in the internal ip address of the sharepoint server and put in the url for the sharepoint site.
Tell the rule that the traffic is coming from the ISA server
Select the listener that you have for your existing site and OK it all.
Now double click the rule
The requests for... should have the public URL for the sharepoint site
the path should be /*
apply the rule.
Create the rule put in the internal ip address of the sharepoint server and put in the url for the sharepoint site.
Tell the rule that the traffic is coming from the ISA server
Select the listener that you have for your existing site and OK it all.
Now double click the rule
The requests for... should have the public URL for the sharepoint site
the path should be /*
apply the rule.
ASKER
Ok...this goes back to DNS questions. On the ISA the External IP should use the ISP DNS? the previous setup had the external looking at the internal nic, the internal listening for DNS and then forwarding it out to the ISP DNS. Now..I guess I aim all intefaces DNS to AD servers that are forwarding to the ISP DNS
Thats certainly how I do mine, and I have rather a significant number of them. I only allow DNS to go out 'through' the ISA and only from my internal AD servers.
ASKER
Talked to Microsoft..here is how we did it
created a smigrate back
- would not work you are not authorized error
- ran smigrate again with -u and -pw commands
- worked
- adjusted an old virtual to be used for wss
- removed the host header for cpor.tnpride.com from the portal virtual server
- restored the host header to the virtual server that will be used for the wss site
- extended the virtual server using wss
- we restored the site using smigrate
- we check that the site appeared internally
- we created a new ISA rule pointing cpor.tnpride.com to cpor.tnpirde.com internally
created a smigrate back
- would not work you are not authorized error
- ran smigrate again with -u and -pw commands
- worked
- adjusted an old virtual to be used for wss
- removed the host header for cpor.tnpride.com from the portal virtual server
- restored the host header to the virtual server that will be used for the wss site
- extended the virtual server using wss
- we restored the site using smigrate
- we check that the site appeared internally
- we created a new ISA rule pointing cpor.tnpride.com to cpor.tnpirde.com internally
Neat :)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER