Re: help detecting webserver on domain

[EMAIL PROTECTED] (Patrick) wrote in message news:<[EMAIL PROTECTED]>...
> [EMAIL PROTECTED] (LGJ) wrote in message news:<[EMAIL PROTECTED]>...
> > [EMAIL PROTECTED] (Patrick) wrote in message news:<[EMAIL PROTECTED]>...
> > > Hi Folks,
> > > 
> > > We had a power outage and my systems went down due to no battery
> > > backups. Everything works once power was restored. However my
> > > webserver cannot be seen on the domain. My domain controller does not
> > > see it and my server does not see the network except itself. I have
> > > tried starting all services but in vain.
> > > Would appreciate any help in this regards. All servers run Win 2000.
> > > thanks
> > > patrick
> > 
> > try a different port on the switch or maybe a different switch or hub.
> > 
> > look at the speed of the nic, maybe it has the wrong settings like
> > 10Mb/s on a 100Mb/s only switch or something like that.
> > 
> > check the subnet of your server and of all ther other systems.
> > 
> > let us know,
> > Lehi Gracia
> > lehig-remove this to [EMAIL PROTECTED]
> 
> 
> thanks for your reply. appreciate your help. i have tried  all the
> things you recommended above but still cannot see my webserver from my
> domain controller.
> My webserver shows all the computers on the network but it does not
> give me access to any. All the other servers dont show the webserver
> in network.
> Please advise. I have spent two days trying to get this working but in
> vain.
> patrick

-see what protocols you are running, make sure you have tcp/ip on the
web server and it has a valid DNS server setting, if you do have it
install then uninstall it and reinstall it, it might be corrupted.
un/install it from the properties of the interface, you will need the
w2k cd for this so make sure you have it available.

-try removing the webserver from the domain and re-inserting it.

-check where your dns settings are pointing to on your webserver and
make sure you can nslookup the domain controller or any other system
from the web server.

-check for any proxy settings or firewall settings you may have. or
the port security in the properties of tcp/ip (unlikely but you never
know)

-check your ipsec settings (unlikely but you never know)

let us know
--Lehi