Member Avatar for singhneeraj421 
In our network we have two gateways one for accessing local intranet sites and other for accessing internet.we use static routing in individual pc to access both the routes.we are facing problem that one intranet site (bD1lbiZjPTQwMCZkPW1pbg==)/ryt/default.htm .we susscessfully ping the site from ip addess and  tracert is also  done successfully but this site is not opening from the browser IE 8.During tracert it is also not showing the sitename but tracert comes susscessfull by ip address.i also  done host entry
  • 2 Contributors
  • 3 Replies
  • 349 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by rch1231

Dani AI

Generated

Good thread — described classic symptoms: IP-level connectivity (ping/tracert) but failure when using the hostname from IE8, and correctly pushed checking routes. Two separate gateways and per‑PC static routes make DNS and HTTP path selection the most likely culprits rather than raw IP reachability.

Two clarifications that help interpret the behaviour: LMHOSTS is a NetBIOS name table—it does not affect DNS lookups used by browsers and nslookup. Traceroute/ tracert shows a hop’s name only when a reverse DNS (PTR) exists for that IP; lack of a PTR will leave tracert showing IPs even if forward DNS works. Also, many web servers use virtual hosting (Host header) so accessing by IP can succeed at network level but still return the wrong site if the server expects the FQDN.

Useful diagnostics (run from the problem client and, where indicated, against the internal DNS server or the web host):

nslookup np41http1.xyx.abc.co.in
nslookup np41http1.xyx.abc.co.in 10.0.0.53    # query specific internal DNS
nslookup 10.20.30.40                         # reverse PTR check
ipconfig /displaydns
ipconfig /flushdns
netsh interface ip show config               # see DNS servers assigned to interface
netsh winhttp show proxy                      # WinHTTP / system proxy used by services
telnet 10.20.30.40 8103                       # basic TCP check to the web port

Interpretation and common fixes: if nslookup to the internal DNS server fails or returns no A record, fix DNS (add an A record or adjust split‑DNS). If forward lookup works but reverse (PTR) is missing, add a PTR if name lookups for traceroute are desired—note PTR absence alone won’t break HTTP. If TCP to port 8103 fails, check host firewall and service binding (server-side netstat/firewall). If DNS looks fine but the browser still fails, inspect IE’s LAN/proxy settings and WinHTTP proxy (WPAD/PAC or a proxy can force resolution via the Internet gateway). Finally, ensure the static routes direct DNS and HTTP traffic for the intranet subnet through the intranet gateway so the client queries the right DNS and hits the correct web server.

Recommended Answers

All 3 Replies

Member Avatar for rch1231

Normally trying to have two gateways is a bad thing. The gateway s the portal through which the system is to send all traffic that it does not have on the local subnet or a route for. Depending on your operating system I would do a route or route print to find out what routes are set up in the system and see if the problem servers subnet is routed properly.

Member Avatar for singhneeraj421

route print shows all the routes.That particular site also gives reply when it is ping.Tracert also successfull.The only thing is about name resolution window is not able to resolve the name from the ip address.If we tracert an ip address of any site then tracert also gives the name of that particular site and offcourse route but when we tracert this site it does not provide us its name. it only shows its route.i have also done entries in lmhost file in windows 7 but it shows no result

Member Avatar for rch1231

Hello,

You probably need an entry in the hosts file (not lmhosts) it is a file in c:\windows\systems32\drivers\etc and it you edit it with notepad MAKE SURE YOU DON'T SAVE IT AS A TEXT FILE. If it has the .txt extension it will not work.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.