unable to see
Results 1 to 5 of 5

Thread: unable to see

  1. #1
    Junior Member
    Join Date
    Sep 2001

    unable to see

    im running win2k with tiny personal firewall and sitting behind a linksys router. i can never surf my schools network and connect to other peoples comps on my schools network unless i drop the firewall and unhook the router. why is that?

  2. #2
    BS, EnCE, ACE, Cellebrite 11001001's Avatar
    Join Date
    Mar 2002
    Just West of Beantown, though nobody from Beantown actually calls it "Beantown."
    Why do you want to "surf my schools network and connect to other peoples comps" in the first place? Do they know what you're doing and why?
    That's Officer 11001001 to you...
    Now you see me | Now you don't
    "Relax, Bender; It was just a dream. There's no such thing as two." ~ Fry
    sometimes my computer goes down on me

  3. #3
    The Iceman Cometh
    Join Date
    Aug 2001
    From what you said, it sounds like you're in a dorm... first off, it's illegal to access other student's computers without their express permission. As for accessing the campus network, you most having something configured incorrectly on either the router or the firewall which is blocking access.


  4. #4
    Senior Member
    Join Date
    Jan 2002
    The whole point of a Firewall is to configure rules to police traffic...Chech your rulesets.

    Routers can have access-lists which perform packet filtering which could also drop a connection.

    [glowpurple]There were so many fewer questions when the stars where still just the holes to heaven - JJ[/glowpurple] [gloworange]I sure could use a vacation from this bull$hit, three ringed circus side show of freaks. - Tool. [/gloworange]

  5. #5
    Senior Member
    Join Date
    Aug 2002
    It definitely sounds like the router is configured incorrectly. Make sure of the network settings (ip and so on...) and also make sure you don't have the router blocking certain traffic outbound from your node.

    Oh, btw, this would be a good time to try using those diagnostic tools built into TCP/IP - tracert and ping - if you haven't already done so. If you can do these successfully, then its probably the configuration/blocking at the router. Hope this helps.
    Opinions are like holes - everybody\'s got\'em.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts