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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

accessing website hosted on network

Status
Not open for further replies.

teash

IS-IT--Management
May 3, 2005
99
US
Hello,

Our current setup has a web server running Windows NT 4.0, a domain controller/file server running NT as well. We are using IIS 4.0, I believe, to host 3 websites.

The clients use Windows 98/ME except for 1 laptop which uses windows xp professional.

Everyone in the world can go to and the pages will be served correctly.

All the clients (our employees) are able to go to and can access our sites.

However, 1 Windows Xp user cannot do this sometimes. He will get a 404 page not found error. Even though the site is up and running. And this is only sometimes. It's a 50/50 chance he will be able access the sites.

All of the computers have a 192.168.1.xxx ip address, and on the xp machine, I have the DNS address as 192.168.1.51 (our NT web server) plus 2 other DNS servers from AT&T.

Before I installed service pack 2, (and this maybe a coicidence) but I could just type in "site.com" and it would find the website. However typing " doesn't work (then sometimes it does).

I don't know where to start the troubleshooting process. I changed the order of DNS servers and it didn't do anything.

I don't understand why it works sometimes and sometimes it doesn't. No spyware was detected, no viruses!
 
I would suggest a few pointers to start with.

On that XP system, what is you connection-specific DNS suffix for the LAN connection? Is it the same as DNS domain setting for your other systems (run "ipconfig" in the command prompt to find out, that is just "ipconfig" on WinXP and "ipconfig /all |more" on Win98).
Try pinging that site by name - does it return the correct IP?
Try doing ping several times, flushing DNS cache between attempts, i.e. ping your site, note IP address returned, run "ipconfig /flushdns", ping again, and over and over. See if it works all the time or fails sometimes.

Good luck.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top