Unable to Ping our Web server

[AGA]

We have a Small Network of 4 servers and 10 users.
1 Small Business Server 4.5 SP 6 (mainly used for exchange)
1 NT 4.0 Server SP 6 (Fax Server)
1 NT 4.0 Server SP 6 (IIS 4.0 Server)
1 Novell 5.01 SP 2 (Application & Print Server)
8 User Windows 98SE
2 User Windows 2000 Professional
1 Net gear Router FV 318 (IIS IP ADDRESS=192.168.0.5)
1 ADSL NEC Modem


Unable to ping our web server's internal Ip address from some worksation whereas from other we can. The Workstion from which we cannot ping --- we cannot browse as well. We can browse all other web site from every workstation. This problem is more of a WINS & DNS RELATED. Could someone please point me in the right direction.

 

[epohl]

If you cannot ping by server by name then it could be a DNS/WINS issue. However if you cannot ping even the ip address more than likely it is a problem with your IP configuration. Check and make sure the subnet mask and gateway are set correctly on the workstation. You should also run a tracert to see where it is failing.

 

[AGA]

All Workstation is set to "obtain IP Address Automatically".

 

[cartwfh]

AGA,

on a network that small you should probably just set up a host file manually match the server names to ip addresses and deploy it to the pc's by log in script. I say this because i did not see you mention that you have a dns server or wins server in the house.

 

[AGA]

But the question is how can some of the PC on our network can ping the Web server and some cant.So the one which can ping can also browse the website--which is exactly the problem on some PC.

 

[TheLad]

On your workstations, you may want to compare the results of running the ROUTE command from a command prompt.

Syntax is: ROUTE PRINT -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[AGA]

Problem Solved
All We had to do was put the details in Lmhost & Host file
IP addresss and Domain name or IP address & Name.

 

[richardb71]

all that did is prove that you have a wins/dns issue yous still have to fix the wins/dns issue
if you are running only one wins server that is easy
stop the wins service, rename the wins folder to winsold create a new wins folder then restart wins.
if you run more than one break the replication first and repair wins like above on every wins server, then reestablish your replication