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

Cannot Access Intranet Website

Hi. I'm new to 2003 server and there is some privelege or service that I am missing preventing me from accessing a port 80 web page on my linksys Wireless access point.

I can ping the ip 192.168.1.245, but no matter what I do HTTP://192.168.1.245 seems to get the standard IE cannot find page stuff. I thought it was to do with the enhanced internet security, but adding a trusted site, and then removing the security has not helped.

I am completely lost as to why I cannot access it. I was logged in as Administrator.

TIA.
0
KyleyHarris
Asked:
KyleyHarris
  • 7
  • 6
1 Solution
 
JamesDSCommented:
KyleyHarris

There is nothing in Windows 2003 other than Enhanced Security Configuration that will affect access to a web site.

Try telnetting to the box with this command:

Telnet 192.168.1.245 80
The screen should go blank

Type GET and press enter to see what comes up. If you get nothing or connection refused then the Lynksys box is not running a webserver on that port at that IP.
If you get some raw HTML and then Connection to host lost then the Lynksys box is running a webserver on port 80 and there is something wrong with the configuration of your Windows 2003 box.

Check your routing, IP Address and subnet mask

Cheers

JamesDS
0
 
KyleyHarrisAuthor Commented:
I'll go try that now. I had originally configured the box in preparation by connecting it to my XP Pro box. so I know that it all is supposed to work.

Essentially there is the 2003 server with a cable to a 6 port switch and another cable from swtich to AP. The purpose to forward to another wireless gateway. I am guessing that some security feature is preventing http access to the ip address.
0
 
KyleyHarrisAuthor Commented:
Tried the Telnet, and turned on network monitoring.

Telnet got a destination host unreachable. Even though I saw the lights flickering on the Access Point the same as the pinging.

I'll try moving it back to the XP Pro box and plug it in just to eliminate the AP from the Server. Certainly its a little confusing.

0
Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

 
JamesDSCommented:
KyleyHarris
it sounds like a routing issue perhaps.

Can you post the output from IPconfig /ALL from the W2k3 box and tracert 192.168.1.245 from the same machine

Cheers

JamesDS
0
 
KyleyHarrisAuthor Commented:
That's a good idea. I dont use tracert a lot. Half my problem is probably my broken leg and the wk3 server 2 levels downstairs :) I'll post the info soon
0
 
JamesDSCommented:
KyleyHarris
yeouch, I did mine last august, still got loads of steelwork and a bad limp

Take your time, falling over hurts and i'm in no hurry!

Cheers

JamesDS
0
 
KyleyHarrisAuthor Commented:
I can't make a lot of sense about what is going on. The only real issue apart from a w3k box is the gigiabit lan card.
I Dunno. I'll make an attempt at hauling the AP and switch back upstairs and plug it directly into my XP Pro. hope you see something I can't

C:\>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : CSNZServer
   Primary Dns Suffix  . . . . . . . : lyon.commsoft.co.nz
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : lyon.commsoft.co.nz
                                       commsoft.co.nz
                                       co.nz

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 CT Network Connection
   Physical Address. . . . . . . . . : 00-11-2F-02-B2-7B
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.1.10
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 202.27.184.3
                                       202.27.184.5

C:\>
C:\>tracert 192.168.1.245

Tracing route to 192.168.1.245 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.245

Trace complete.

C:\>



0
 
JamesDSCommented:
KyleyHarris

IP config and tracert is ok

It sounds like the linksys box is denying traffic to it's web interface. Have you looked at its config to make sure it is actually serving a web site and it's talking on port 80?

Cheers

JamesDS
0
 
KyleyHarrisAuthor Commented:
The only method of talking to it is port 80 :) that I'm aware of. Maybe i better go see if it has a telnet port 22 or something
it was working fine before.
0
 
KyleyHarrisAuthor Commented:
Well. I connected the switch to an XP Pro box, and it talked to the thing with no problems at all and I configured it how I need. This doesn't solve my problem though, that the win 2003 server wont talk
0
 
JamesDSCommented:
KyleyHarris
Can the W2k3 box talk to other websites?

If the linksys box is java based, then Windows 2003 probably won't work as it does not have Java installed by default.

Cheers

JamesDS
0
 
KyleyHarrisAuthor Commented:
Managed to get the 2003 Server accessing websites etc. The problem was the local
domain policy on IP Traffic. Which had to be set to allow communications with other
computers.

2003 server is locked down so tight by default it almost cant even see and use itself.

I'll award the points for the assistance and effort.
Thanks.
0
 
JamesDSCommented:
KyleyHarris
Welcome, thanks for the points

Cheers

JamesDS
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now