Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

can't see website from within network 4

Status
Not open for further replies.

rareswan

Technical User
Dec 19, 2000
22
US
We had a small flurry of catastrophies recently so I can't pinpoint the causing factor, however the problem is this.
We have our own webserver for our website and the website is visible to anyone outside of our network but can not be accessed by any of the workstations within our network. We have four servers "Main", "Backup", "DNS", "Web". We have about 30 workstations most running NT with a couple of 98's all running on NT Server. Oh yeah I can't ping the webserver from anything except the backup server. Any thoughts out there. Thanks for any help.
 
Is there a Firewall in the System which blocks the server to all computers except the Internet?

hnd
hasso55@yahoo.com

 
might need to put WINS and DNS settings in for each workstation. also in internet explorer put a check in the box for local addresses and give the local address missing out the http:// part ( e.g. NOT BUT just If in doubt get the Ball Pein Hammer out
 
Thanks for the quick responses

We have no firewall and I should have mentioned that we run two domains, one for the internet and one for our network. One server on the network has 2 nic cards one going to the network hub and the other going to our web server. The web server has 2 nic cards the one coming in from the network server and the other to our DSL line. The network server can see our website and our workstations can see the network server. We run DHCP on the network server to handle the WINS and IP addresses, our DNS server is on our internet domain. The hammer I use only on myself as I wouldn't want to hurt it on the hardware.
 
Use tracert from one of the "blind" workstations. Where it dies is where you need to start looking. I suspect you lost a route on the multihomed NT box. Let us know the results of the tracert

Mike S
 
Mike

Tracert just returns with "1 Destination host unreachable" when the blind workstations are directed towards the website however it responds positively when pointed towards the server the website is on.

Randy
 
It seems your DHCP server not giving you Default Gateway, Since you have dual home PC's , any traffic routed to the Web server forwaded throgh the dual homed eth.
c:\>route print
you should see an entry with
0.0.0.0 <ip of dual homed PC> entry.
If it is not their Check DHCP SCOPE or Restart DHCP Service
 
I would agree with mbhandari starting point. I have seen this where DHCP has gone &quot;stupid&quot; or is misconfigured. I have also seen it where yours truely :) mistyped a new subnet ID on the workstation which did not match the network I was on. Given this is spread across many workstations either the server routes are screwed up ( dual home NT does have it's problems) or DHCP. Just as a warning, I worked on a dual homed box that quite routing after a crash/reboot. We had to to pull the NICs, pull TCP and reinstall NICS with TCP inorder for it work again. Why? who the hell knows.. I think something very subtle was corrupted in the IP stack and dual homing seems to be somewhat precarious to start with.

Mike S
 
~~I work with rareswan~~

DHCP seems to be working correctly. All clients renew their IPs with no problems. Also, the clients are getting the IP of the DNS server but is seems as if they (the clients) cant find their way to the DNS server. We do a 'nslookup' and it shows that they are looking for the correct ip but they just cant find it.

Within DHCP manager, I have a dns server (with correct IP) assigned in the 'Option Configuration'.

I dont know if it helps but, in network neighborhood we can get into the webserver (it's the pdc on that domain) but we can not get into the dns server (it's the bdc for that domain).

Thanks for the help.

Abel
 
here's the answer for those that need it in the future.

While doing an 'ipconfig /all' on the workstations I noticed the gateway address was blank. Now, within DHCP manager I had already set the dhcp option of router to a nic on the internal BDC. But, I had set it up under the 'scope configuration' and NOT the global configuration. Once I added the gateway/router to the global....everything worked.

Abel

 
All who responded

Thanks for the help your time and consideration. Thank you especially wybnormal (not a clue) and mbhandari. And thank you Abel for fixing this so I don't have to screw around with it anymore.

Randy
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top