I will start by saying I am not a system admin. I work as an intern at a construction company doing mostly hardware/software support.
I also publish changes to their website with Dreamweaver. I was alarmed to see that how I was told to configure Dreamweaver, it is basically set up to publish directly to the live remote server.
The website is hosted in-house using IIS on Windows Server 2003.
I would like to setup a test site to publish to before pushing new documents to the live website. I can not simply preview pages in my browser due to the website using sever technology specifically ASP.
I do not want to install IIS on my local machine. My idea was to create a test site on the same server the actual site exists on. I basically followed instructions listed here: http://support.microsoft.com/kb/323972 . I just tried to mirror the settings for the actual site to the test site. I then took all the files from the directory of the actual site and copied them to the directory of the test site.
I have not been able to get this to work however. The actual website is configured to be on the internal address 126.96.36.199. The test site is configured to be on 188.8.131.52. If you try to access .238 the connection times out.
I thought maybe just some services needed to be restarted. I have restarted the IIS services and DNS services to no avail.
What am I missing??
Edit: Additional Info.
The server running IIS is local 184.108.40.206. There are a couple sites hosted from this IIS server. If I run ipconfig from the server. It lists .229 as well as .240, .241, .243, .245; but no .238. I assume this is where my problem lies. How do I fix this?