Sorry, I was busy :)
Now, so you have 2 IP in each host, with 2 hosts you got 4 IP address for
the websites in the IIS server.
With round-robin DNS, it will returns the next host ip address in the DNS
records, which merely just give the client IP addresss, the client which
then take the IP and connect to the IIS host.
You are saying now if you have machine ON with 2 IP address, you don't see
this issue?
but you bump into this when you have another machine ON with total of 4 IP
address?
Let's do a simple analysis..... where do you think the problem is?
2 IP addresses 1 host - no issue
4 IP address 2 hosts - issue found
While you can skip the DNS part, as I don't think they will be any issue
with that.
of coz - make sure with 1 host 2 IP, you have got client talking to the 2 IP
addresses, not just one.
So, again - this would be tough to troubleshoot. but I would suggest you put
in tracing code, like response.write ip address, etc
to help you keep track of those important variable. then from there find out
why is missing, etc?
I still feel that this is coding issue.
--
Regards,
Bernard Cheah
http://www.iis-resources.com/
http://www.iiswebcastseries.com/
http://msmvps.com/blogs/bernard/
Post by smokehouseDear Bernard
??????????????????????????
?? ???IIS ?? , ??ASP&???? , IIS???IP .
??IIS???????????????IP (?????IP )
??IIS???????????????IP ( DNS???????IP )
DNS Server???FQDN?????IP , ????IP??????
???????????? , ???????? .
????????????? , ???????????? .
?????????????????????
??????
????????? : ????DNS??????????
???????IIS?? , DNS???????? .
??????????????????? ,
?????????????
??????
Cloud
Post by Bernard Cheah [MVP]I still not sure where is the problem.
So you are NOT running NLB, instead you use DNS round robin, to direct
request for you two IIS hosts.
As for the session timeout warning, I think this is application related,
because once you are connected to one of the IIS, you are not asking the DNS
again, and your browser is expected to communicated to that ONE particular
IIS during the entire session I believe.
To test it out, if you connect directly to one of the IIS host, after idle
for a while, I think you will get the same warning message.
--
Regards,
Bernard Cheah
http://www.iis-resources.com/
http://www.iiswebcastseries.com/
http://msmvps.com/blogs/bernard/