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

Cannot see local webserver

HELP!!!

We have an older Win2000 server that runs telemetry, polling legacy sites and sending out email/text messages to the appropriate people.  This was initially isolated behind its own firewall.  Not really sure why, it was set up that way years ago and worked fine that way.  Said firewall went under last week, causing the server to have to be brought into the fray with our other machines.  I am having a strange problem that I couldn't seem to find any precedent for in my troubleshooting search.  

This server can be accessed within the network via RDC and can be pinged successfully, but cannot be "seen" by any of the other terminals in its workgroup via My Network Places, nor can it "see" any of the terminals from its end.  

IIS is running on the server and has port 801 open for hosting the site.  The local machine is running the site just fine.  However, if I attempt to run the site from a workgroup computer via http://192.168.0.40:801, I get nothing.  Further, I get nothing when attempting to access port 801 through our public ip address so this is a not strictly limited to LAN.  I cannot seem to find evidence of any firewall software running on the server that would run interference on port availability...

Also, our SQL Mail service seems to have stopped as well.  This (I believe) is supposed to be handled through STMP via port 25?  I thought that these two problems were independent of one another but would like some feedback on this as well.
0
Titus57
Asked:
Titus57
  • 10
  • 6
  • 2
  • +1
1 Solution
 
ragnarok89Commented:
Is the Win2000 firewall on, and blocking port 801? Does it perhaps only allow https?
0
 
jimponderCommented:
What is the Gateway of this Win2k machine?  Seems to be different than the rest.  Perhaps it is the IP of the dead firewall?
0
 
Titus57Author Commented:
The gateway is 192.168.0.1, same as the other machines in the workgroup.  There is no native firewall included with Win2k Server, right?  I was unable to locate it if so.  The weird thing is that port 801 worked fine with the old firewall.  I didn't monkey with the port settings in IIS.
0
Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

 
kdearingCommented:
It's possible that the old firewall was doing port translation.
Get into the Win2k server's IIS settings and check what port it is configured for.
0
 
Titus57Author Commented:
The IIS is configured for port 801.  If I pop in http://192.168.0.40:801 into the server's web browser, the page loads fine.  If I try this on any other computer in the workgroup, it doesn't.  What's confusing is that there is the ability to connect and see the computer from within the network via ping and RDC, but the TCP port that's opened for webhosting cannot be seen.  I have tried changing the port from 801 to see if that would help, but no dice.
0
 
kdearingCommented:
OK,
Network obviously works because you can ping and RDP
The IIS services are running because you can access it from the machine itself

The only thing left I can think of is some kond of firewall application
Win2000 doesn't have a native windows firewall

Some antivirus packages perform basic firewall functions
0
 
Titus57Author Commented:
There is no software firewall application running, as far as I can tell.  Is there any kind of port analysis software that I can install on a Win2K Server machine that would help identify what's clogging my ports?  Most of the software available has a hard time running on that platform due to its legacy status.

There has to be a way of isolating the root of the problem.  Under normal circumstances, a Win2K Server machine located in the same workgroup could be seen by the other computers even if they are all XPs and 2003 Servers, right?
0
 
kdearingCommented:
To see what ports are open, you can use the NETSTAT dos command:
http://www.petri.co.il/quickly_find_local_open_ports.htm
0
 
Titus57Author Commented:
Here is what NETSTAT reported:

Listening Ports:
  TCP    0.0.0.0:21             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:25             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:53             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:515            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:548            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:801            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1433           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1801           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2103           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2105           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2107           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3001           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3002           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3003           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3004           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3006           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3070           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3071           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:6614           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:8080         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:11223        0.0.0.0:0              LISTENING
  TCP    192.168.0.40:139       0.0.0.0:0              LISTENING

Open Ports:
  TCP    192.168.0.40:801       192.168.0.40:13260     ESTABLISHED
  TCP    192.168.0.40:3389      192.168.0.69:12384     ESTABLISHED
  TCP    192.168.0.40:13260     192.168.0.40:801       ESTABLISHED

If I close out the browser session with the local webserver pages, then the 192.168.0.40 lines go away, leaving just the RDC port open.  Any insight?
0
 
Titus57Author Commented:
Check that, I meant the 192.168.0.40:801 lines go away... Oops
0
 
kdearingCommented:
The only other thing I can think of is the telemetry software itself.
It's possible that it will only accept connections from certain IP addresses, or some other restriction.
0
 
Titus57Author Commented:
Well, if that is the case, then how can the lack of visibility from the system level be explained?  And how is it possible to reach a LAN computer within the same subnet via RDC/ping yet not through the workgroup/webserver portal?
0
 
jimponderCommented:
Anything on this IP? 192.168.0.69:12384
I noticed it was diff't than the rest...
0
 
Titus57Author Commented:
That is the ip address of the computer I am initiating the RDC from.  Port 3389 is set up as the RDC Tunnel.
0
 
kdearingCommented:
The telemetry application is listening on port 801; it can control connections to this port.
The fact that you can ping and RDP tells me the problem is with the application itself.
0
 
Titus57Author Commented:
That still doesn't answer the question as to why I cannot "see" this computer within the workgroup and vice versa...  Under normal circumstances, a Win2K Server machine located in the same workgroup could be seen by the other computers even if they are all XPs and 2003 Servers, right?
0
 
kdearingCommented:
If the Pcs are members of a domain and the Win2k server is not, then they may not "see" each other.
0
 
Titus57Author Commented:
I fixed the problem by migrating the application over to a freshly wiped/restored Win2k3 server running MSSQL2005.  KDearing's theory that the application was to blame turned out to be incorrect, as the application is running fine in the new environment and again accessible on the web... the only change that had to be made was in the myconn string for the initial database connection inside of the project's vb code.  Thanks for everybody's help.
0
 
Titus57Author Commented:
Fixed the problem myself
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

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