• April 20, 2025, 01:45:40 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: problems with firewall settings and browsing HTTP server on internal ip address  (Read 7414 times)

karenS

  • Guest

Hi there I have a IIS set up on my computer and am able to to browse the default website at http://localhost/ as well as locally from its IP address of http://192.168.0.193

however when i try and access this ip address from a browser on another computer withing the same network it does not work. the page times out

I am assuming this has to do with a firewall setting however I tried changing all the settings up with no luck.

I tried creating a virtual server and port forwarding rule but still no luck..

I just did a reset on the router so the settings are at the factory specs.

can anyone help me with this issue please and thanks?
Logged

Element

  • Level 1 Member
  • *
  • Posts: 22

Try disabling SPI on the router which can be found under Advanced>>>Firewall Settings and see if that helps
Logged

karenS

  • Guest

thanks for the suggestion however when I disable the SPI setting this does not fix the problem in fact after changing that setting and rebooting the router I am unable to connect to any webpage on any of my computers.

Re-enabling it and rebooting the router allows me to connect again
 :(

Logged

Fatman

  • Level 9 Member
  • ****
  • Posts: 1675

The problem is the firewall, on your PC.

Please ensure that both PCs have their software firewalls turned off, at least for testing purposes.
Logged
non progredi est regredi

Matteo

  • Guest

do you have WINS or DNS configured?  also the setup you have requires peer to peer sharing on (unless im totally wrong) (I might be)....
Logged

D-Linkuent

  • Level 1 Member
  • *
  • Posts: 15

The problem is the firewall, on your PC.

Exactly.  Begin by disabling the firewall on the machine running IIS (Windows Firewall?).
Logged