General discussion

Locked

How to configure IIS for intranet only

By cyberbiz ·
We're running IIS 4.0 on a NT 4 server.
We have a browser based application (EATEC) and the application runs faster when we connect the server to the internet.

Without it, it takes over a minute to login using the intranet (wired ethernet connection). With the internet connection enabled on the server, login takes 2-3 seconds.

Obviously, IIS is looking for something on the internet but what? Or is it the application?

All services (ftp,smtp) except the web service are stopped.


Any thoughts?

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

How to configure IIS for intranet only

by curlergirl In reply to How to configure IIS for ...

This might possibly be a DNS/name resolution problem. Do you have an internal DNS server running or are you using an ISP's DNS servers? Are your workstations pointing to the internal or external server as the primary DNS? What IP address is your IIS server using - internal or external? If the workstations are pointing to an external DNS server (at your ISP, for example), and/or if the IIS server has only an external and not an internal IP address, then they would have to use the ISP's DNS servers to resolve the IP address of your server. Is there any proxy server or firewall involved? Lots of questions need to be answered. Hope this helps!

Collapse -

How to configure IIS for intranet only

by cyberbiz In reply to How to configure IIS for ...

Thanks a lot for the help.

Turns out it was an application issue.
The application (Eatec) was looking for
help files on the eatec server when attempting to log in.
Changing this setting solved this issue
and it was accidentally discovered when
going through several .ini files.
Thanks again.

Collapse -

How to configure IIS for intranet only

by eBob In reply to How to configure IIS for ...

I agree that it sounds like a name resolution problem.

Although I am not sure what you mean by "when we connect the server to the Internet". Do you mean "when we have our Internet connection UP"?

The scenario is likely: when your network is connected to the Internet, your clients try to find the address of the server "intranet.mycompany.com" using DNS. But they're pointed to the DNS at your ISP which replies right away "I don't know that system". So then your clients fall back to using WINS or whatever, and find the server fairly quickly.

Without the Internet connected, DNS tries but cannot find the DNS server at your ISP. But in the "never say die" way things like this are, it keeps trying for some time. Eventually it gives up, and the clients fall back to WINS.

If this describes what you're experiencing, then there are a couple of approaches you can take.

One is a Registry hack to tell Windoze to try WINS first, then fall back to DNS second (rather than the other wayaround).

The other is to install DNS internally. Tell your Internal DNS to pick up records from your ISPs DNS server(s), and also create a ZONE file to identify the systems on your Intranet. Then point all of your clients to this internal DNS.Hope that helps...

Collapse -

How to configure IIS for intranet only

by cyberbiz In reply to How to configure IIS for ...

Thanks a lot. This is correct but the
application was looking for a server
(www.eatec.com) in one of its .ini
files for help info. The vendor of the application did not give me this information, I found it by accident while re-installing everything and re-checking.
Thanks a lot.

Collapse -

How to configure IIS for intranet only

by cyberbiz In reply to How to configure IIS for ...

This question was closed by the author

Back to Windows Forum
5 total posts (Page 1 of 1)  

Operating Systems Forums