• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5265
  • Last Modified:

Can ping/telnet to website, but can't browse to it.

Good morning, experts.

I'm having some strange issue with a few of my servers.  


I'm trying to browse to a website hosted in my DMZ, however IE just hangs there and won't do anything.


I can ping the website.  I can telnet to the website using ports 80, 81, and 443.  That tells me this isn't a firewall issue.  Also, there is nothing of importance in my firewall logs.  Other servers on the same subnet can browse to the website just fine.  


I've also tried installing Firefox to see if it was an IE issue, but nothing.  



Any ideas?


0
Rogiee
Asked:
Rogiee
  • 6
  • 4
  • 3
  • +2
6 Solutions
 
exhaustCommented:
Can you try adding the exact URL you are having trouble with to IE's Trusted Site. Does it now allow you to load the website?
0
 
RogieeAuthor Commented:
@exhaust

Same results after adding.
0
 
exhaustCommented:
Ok, if you can telnet to these ports you definitely have an end to end network socket connection to it. It almost sounds like that the website your running isn't listening on the default ports. Check IIS (I'm assuming that's what you're using).
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
jfields71Commented:
Have you tried watching network traffic on the host to see what, if any, traffic is passing between the two machines?  Try Wireshark: http://www.wireshark.org/.  Perhaps packets are dropping or the connection is not being completed.

Also, have you tried a simple text tool like wget to see what is being transferred?  http://en.wikipedia.org/wiki/Wget.  
0
 
RogieeAuthor Commented:
@exhaust ~if that were the case, i wouldn't be able to get the to website at all.  I can get to the website fine from serverA.  Server B is on the same subnet and configured the same way, however it is unable to get the the site.
0
 
kadadi_vIT AdminCommented:
Is any Internal DNS server configuration problem on server B ....:)...so its not resolvign the site URL.

Regards,

VIjay Kadadi
0
 
RogieeAuthor Commented:
I can ping the hostname fine, so not DNS.  ;o(
0
 
ChiefITCommented:
Go into the HOST and LMHOST files and remove anything except the loopback addresses. Those files will be looked at by your client prior to going to a DNS server or the Master browser for a DNS query or Netbios query. If they are configured without that address, you will get the types of problems you are seeing.
0
 
ChiefITCommented:
Oh, Yes:
Host is located at the C:\i386\Host and can be edited with a text editor like notepad.
LMHOST can be found in two locations C:\i386\LMHOST and C:\ Windows\System32\dirvers\ect\LMHOST. That too can be edited with a text editor like notepad.
0
 
exhaustCommented:
C:\Windows\System32\drivers\etc\hosts
0
 
RogieeAuthor Commented:
HOSTS and LMHOSTS are empty...


As I said before, I can ping by hostname, so the HOSTS file shouldn't matter...


0
 
ChiefITCommented:
What computers do you see in My Network Places?
0
 
RogieeAuthor Commented:
I cannot see the server hosting the website in My Network Places.   I'm assuming that's because it is in the DMZ though.


I am able to ping it.  Telnet to it.  UNC to it....
0
 
ChiefITCommented:
This is a browser issue:

The browser uses netbios broadcasts. Netbios broadcasts will not go over a VPN tunnel, across many firewalls, or through any sort of NAT to a different subnet. Since this is the case, the browser needs help. It needs to be configured with WINS.

Here is a article on the browser service. I highly recommend anyone with browser problems read this article. This may be a NT4 article, but the browser service has not changed at all. The only thing is a registry key for 2003 server. The NT4 registry key is "IsDomainMasterBrowser". The 2003 server shortened that up to "IsDomainMaster".

Here is your fixe::: On each subnet, you will want a master browser and backup browser. Then, on the main DC, you want to make sure it has the ability to communicate as the Domain Master Browser. Master browsers on different subnets will communicate with the domain master and populate a list of nodes. In your situation, you might consider the WINS/WAN configuration of the Domain master browser.

http://www.microsoft.com/resources/documentation/windowsnt/4/server/reskit/en-us/net/chptr3.mspx?mfr=true
0
 
RogieeAuthor Commented:
Thank you all for your help.

It ended up being the MTU setting on the server.  I changed it to 1320 and it works now!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 6
  • 4
  • 3
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now