Need help with guest accounts
in [Mac Systems]
|
Prev: iPad
Next: Credit card jam, was: Black Screen of Death
From: Kathy Morgan on 8 Feb 2010 12:49 Jolly Roger <jollyroger(a)pobox.com> wrote: > In article <1jdk6sm.afjjbzbq2kvcN%kmorgan(a)spamcop.net>, > kmorgan(a)spamcop.net (Kathy Morgan) wrote: > > > We have only one network, hiding behind a DSL > > router and switch. > > > (One of them--probably the switch?--blocks incoming > > http requests and I don't know what else--I'm waiting for a more > > knowledgeable person to help me fix that.) > > That would be the router. You'll need to connect to the router's > web-based control panel and map port 80 (and possibly 443 if you are > running HTTPS) to the machine running the web server. Thanks. I knew port 80 was used for HTTP but I didn't know what port was used for HTTPS. > > Our network has the ancient Windoze patron computer, an iMac, and a Win > > 2003 Server. > > Just so you know, speaking as a system administrator of many years, > that's a horribly insecure choice for a web server. A cheap Mac mini can > serve web pages more securely, and probably more reliably to boot. A Mac server would have been my prefered choice at the time we bought the server. Unfortunately, the software which maintains the online cataloging and creates the web pages only runs on Win 2003 Server, so I'm stuck with it. -- Kathy
From: nospam on 8 Feb 2010 13:10 In article <1jdl5fr.76hjfd1bqwg2pN%kmorgan(a)spamcop.net>, Kathy Morgan <kmorgan(a)spamcop.net> wrote: > I agree completely! This may be an argument in favor of a router with > poor range. If we could force them to come inside the building, or even > very close to it, where they're under our eyes, that might help > discourage some of these activities. many routers provide for adjusting the transmit power, but anyone intent on wanting to use your network can buy a big antenna. the best thing to do is secure it with a very good password but that has its drawbacks for a public access system. > That would protect our network, but wouldn't it allow the guest to > commit the offenses you mention in the first paragraph? While I think > it's highly unlikely to happen, I wouldn't want to enable some hacker > who happens to be touring through my neighborhood to control his Botnet > from our guest WiFi access. A more likely scenario would be a local > highschool kid using it to pirate music and software, and that would > also be unacceptable on several levels. a lot of routers can block specific protocols or web sites. for instance you could allow only port 80. although it's still possible to do illicit things over just port 80, the bar is that much higher and you have proof that you took steps to block it.
From: Kathy Morgan on 8 Feb 2010 13:46 Michelle Steiner <michelle(a)michelle.org> wrote: > With an Airport Express, you won't be able to connect any computers to it > via ethernet; the only ethernet port on the Express would be connected to > the DSL modem. > > But I just noticed you said you have a switch. I'm a bit puzzled as to how > things are connected now. Our Internet access is provided by a DSL modem which is connected to an ethernet switch with approximately 10 or 12 ports. (I'm at home now, so I can't look at it to confirm--there are a *whole* bunch of ports, maybe 20 or 30, but I'm not sure they're all active and available for use.) Each of our computers and printers is plugged into one of those ports. If I got either an Express or other wireless router, it would be plugged into one of the empty ports on the switch. -- Kathy
From: Daniel Cohen on 8 Feb 2010 14:13 Jolly Roger <jollyroger(a)pobox.com> wrote: > Also, automatic > updating will not be on by default, and many such routers barely get any > updates anyway. You do get what you pay for. What kind of updates would you expect to need? I've never updated my router(s). Maybe I'm missing something important. -- <http://www.decohen.com> Send e-mail to the Reply-To address. Mail to the From address is never read.
From: Kathy Morgan on 8 Feb 2010 15:09
Michelle Steiner <michelle(a)michelle.org> wrote: > Ah, that clarifies (and somewhat changes) things. In this case, you would > need to set up the router as a bridge. And with that I'll bow out because > there are people here more knowledgeable than I as to what and how you > would need to do things. Aagh! Now you've introduced a new term that I don't even know. I'm off to wikipedia. -- Kathy |