Answers
Jan 03, 2008 - 05:58 AM
I've never encountered a program that runs on windows 2k and not on XP.
furthermore XP pro includes IIS5.0 (win2k3 server has 6.0)
what you'll have to watch out for are firewall and tightened security issues. watch folder security settings as well as folder sharing and make sure you configure windows firewall correctly.
furthermore XP pro includes IIS5.0 (win2k3 server has 6.0)
what you'll have to watch out for are firewall and tightened security issues. watch folder security settings as well as folder sharing and make sure you configure windows firewall correctly.
Jan 03, 2008 - 07:41 PM
Thanks for your prompt response. Oracleof Delphi........
But do I need to really check folder settings,firewall and other security issues.???
I doubt it, as I mentioned earlier, applications are web based (intranet) and running on the same server ( Windows 2000 server) for the both OS. ( Windows 2000 professional and Windows XP professional).
or I didnt get your word.? Can please elaborate it?
Regards,
Sarbjit
But do I need to really check folder settings,firewall and other security issues.???
I doubt it, as I mentioned earlier, applications are web based (intranet) and running on the same server ( Windows 2000 server) for the both OS. ( Windows 2000 professional and Windows XP professional).
or I didnt get your word.? Can please elaborate it?
Regards,
Sarbjit
Jan 04, 2008 - 07:14 AM
you probably don't need to check folder settings, since you're moving from less secure to more secure. It is possible that the IEUser account (an account that is created by IIS for web browsers) won't have access to the folder contents that hold your website. Also since IIS is already setup, service pack 2 (specifically windows firewall) doesn't automatically open port 80. you'll probably have to manually allow that exception, it's just a box to check.
One thing about your last post that is confusing me now is that you mentioned windows 2000 server, I don't believe windos XP pro is an upgrade to 2000 server edition, but it's definitely an upgrade to 2000 professional edition.
One thing about your last post that is confusing me now is that you mentioned windows 2000 server, I don't believe windos XP pro is an upgrade to 2000 server edition, but it's definitely an upgrade to 2000 professional edition.
Jan 06, 2008 - 08:12 PM
OracleofDelhi, thanks for your prompt responses.
Well let me clear things, I am going to move from Windows 2000 professional to Windows XP professional edition OS on my pc.
I have my applications ( web based intranet application using ASP ) running on my server ( Windows 2000 server edition).
What I have understand is that, I need to check IEUser account for folder contents that hold my website content on my server ( i.e on Windows 2000 server). Is that you mean?
But I am not doing any change in my server.I am just changing my OS on my pc.So will it affects my applications?
I read that ASP handles all the request on server side.So there is role on client except sending the request. Is am I correct?
Regards,
Sarbjit
Well let me clear things, I am going to move from Windows 2000 professional to Windows XP professional edition OS on my pc.
I have my applications ( web based intranet application using ASP ) running on my server ( Windows 2000 server edition).
What I have understand is that, I need to check IEUser account for folder contents that hold my website content on my server ( i.e on Windows 2000 server). Is that you mean?
But I am not doing any change in my server.I am just changing my OS on my pc.So will it affects my applications?
I read that ASP handles all the request on server side.So there is role on client except sending the request. Is am I correct?
Regards,
Sarbjit
Jan 07, 2008 - 07:11 AM
yes, you are absolutely right. the server handles ASP requests, the client sends requests under the IEUser account (which IIS automatically sets up). both Win2000 and WinXPPro use IIS5.0, so your applications will work. Are you using frontpage server extensions as well?
Jan 07, 2008 - 07:23 AM
if you go through the IIS wizard again to set up your website you won't need to worry about any IEuser account privilage issues and you can just concentrate on the firewall. If you are using FPSE (front page server extensions) than you need to the two items listed in the server health section on the following website on your server:
http://127.0.0.1/_vti_bin/_vti_adm/fp...
note that 127.0.0.1 is the loopback address, replace it with the local ip address that your server is answering the website requests on if it is not set to "any"
http://127.0.0.1/_vti_bin/_vti_adm/fp...
note that 127.0.0.1 is the loopback address, replace it with the local ip address that your server is answering the website requests on if it is not set to "any"
Add New Comment