IIS before email

  • Thread starter Thread starter Steve Grosz
  • Start date Start date
S

Steve Grosz

I'm curious as to why someone who users our server for
email and viewing their web pages is forced to call up a
web page hosted on the server before they can get the
email to work?

What happens is this. If they view a web page on the
server and then remotely use outlook or another email
program to connect and get their email, the users can get
to the email server fine.

If they try to get the email first, without browsing to a
web page, the mail program fails to connect.

Any thoughts?

Steve
 
I'm curious as to why someone who users our server for
email and viewing their web pages is forced to call up a
web page hosted on the server before they can get the
email to work?

What happens is this. If they view a web page on the
server and then remotely use outlook or another email
program to connect and get their email, the users can get
to the email server fine.

If they try to get the email first, without browsing to a
web page, the mail program fails to connect.

Any thoughts?

First thought would be that it probably doesn't involve DNS. Second
would be that when you post to the IIS group, you include details
about what you mean by "fails to connect." Log entries would help,
error messages, description of what you think is supposed to happen
that isn't, etc.

Jeff
 
I am with Jeff as this probably not being a "DNS problem"
since apparently DNS does work.

My first thought would lean towards AUTHENTICATION.

What type of authentication is your web site doing?
What type of email server?

How many domains are involved? Where are the user accounts?
 
Back
Top