Installed Domain network, now no Http access...

[steverbs]

Hi all.

We have recently installed a Windows 2003 Server as a domain controller (we have moved from a work group) and have found that we are no longer able to access eachothers development machines via HTTP (We can get to them accross the network though). Previously, for testing purposes, we would be able to run our websites accross the network (i.e. ComputerName/IISVirtualDirectory/Default.aspx), however, this now results in the MSN 'Can't find what your looking for' screen.

Any ideas on what could be causing this?

Stephen.

 

[aftertaf]

do you have the same problem when trying via IP address? this could be a name resolution problem... does DNS work correctly otherwise?

and on each machine, are the web services up and running and the correct accounts have rights to access them? if you try

http://localhost,

do you get the local page?

Aftertaf

"Solutions are not the answer." - Richard Nixon

 

[steverbs]

Yeah, all of the settings appear to be ok. Localhost also responds correctly when run locally.

However, we have just looked into problems with the IP/DNS and have found that those with static IPs are able to respond to HTTP requests just fine over the network, so we will look further into that.

I'll let you know how we get on.

Thank you.

 

[aftertaf]

if you have a routed network, make sure default gateway options are setup ok in DHCP....

Aftertaf

"Solutions are not the answer." - Richard Nixon

 

[steverbs]

It was the static IP in the end. We set these up on the problematic machines and restarted everything and it all seems to work fine.

Thanks for your help.

Stephen.