• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 749
  • Last Modified:

Ilient SysAid and DNS issue

I am trying to set up IIient Sysaid on the Windows 2003 server that has nameweb domain and trusts nameworld that is the local domain in our network.

There is sharepoint that runs on that server as well on port 8080

So far I set up Sysaid so that internal users can access it by typing 10.x.x.x:8081
Sharepoint uses 10.x.x.x:8080.

I would like to set it up the way that will allow internal domain users and external users to access Sysaid by typing support.domainname.com.

Sharepoint users can access the server from the outside just fine. It is with sysaid that I struggle.
Any advise would be appreciated. Thanks.
0
etraxler
Asked:
etraxler
  • 3
  • 3
1 Solution
 
Chris DentPowerShell DeveloperCommented:

My initial thoughts are that you can use Host Headers to separate the queries out to each site. I'm assuming the SysAid part runs under a website?

Chris
0
 
etraxlerAuthor Commented:
Host Headers? Please explain how you think it may work.
Thanks.
0
 
Chris DentPowerShell DeveloperCommented:

Host Headers are used to filter a name to a specific site in a web server like IIS. That means that you can host multiple sites on the same port and IP, where the only difference is the name used to access the site.

If these systems run under IIS then we would set a Host Header by opening the Web Site Properties, then selecting Advanced under the Web Site tab. Either add a new entry to the web site identities box, or modify the existing value.

It means that instead of this:

SysAid: 10.x.x.x:8081
Sharepoint: 10.x.x.x:8080

That we could do:

SysAid: support.domainname.com
Sharepoint: www.domainname.com

Both would appear to run under TCP Port 80 (HTTP) to the outside world, and from what I gather, on 8080 from inside your network, although you would still have to add on the port number for internal access.

Chris
0
A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

 
etraxlerAuthor Commented:
I am sorry for not replying to you.
Should I create a page in IIS with the port 81?
Thanks.
0
 
Chris DentPowerShell DeveloperCommented:

> Should I create a page in IIS with the port 81?

If you're using Host Headers both can run on TCP Port 80. If not, you'll have to bind either a separate port, or a separate IP address to those sites.

Chris
0
 
etraxlerAuthor Commented:
I created a redirection in IIS to port 8081 and it worked. I will give you points since you directed me to the solution.
Thanks!
0

Featured Post

What Security Threats Are We Predicting for 2018?

Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now