because my server is online! woohoo. and configured a IP cop for it, that wasnt much fun. but iv got one complication my group policy to re-direct my documents folder so that everything saved is on the server, group policy doesnt wanna work argh! but thats a minor complication really. woohoo excited!

---

We are all born ignorant but one must work hard to remain stupid

considering we were so far behind with it yes. the firewall was the worst i think. fotgot to change the gateway on the client haha couldnt get to the interwebz. derr o well back to it i guess.

---

We are all born ignorant but one must work hard to remain stupid

oohh yea even better is i crimped my own ethernet cables today. woohoo. proved hard with tendonitis in my wrist tho but it works well. now im just playing with speedtest and i think my pings were pretty deplorable. what are yours?
"/>

Edited by Nat.W¿LL¿: 14/11/2008 06:18:41 PM

---

We are all born ignorant but one must work hard to remain stupid

just finished what 'should' be my last programming class for the year (got a test to go thats it) see what i made. its quiet handy makes the windows log easier to read in a HTML format

---

We are all born ignorant but one must work hard to remain stupid

Speaking in a purely professional capacity Nat, I must say,your signature is spot on.
Nice work, by the way

---

Mistakes are a part of being human. Appreciate your mistakes for what they are: precious life lessons that can only be learned the hard way. Unless it's a fatal mistake, which, at least, others can learn from.

Ask questions. There's no such thing as a stupid one, just stupid answers. (mostly)

"That", is a conjunctive pronoun, silly. As if you didn't know.

Cheers

Malai5

---

THE FURTHER YOU GO, THE LESS YOU KNOW!
www.mam3.com.au

yea tell the tafe that. not me.

---

We are all born ignorant but one must work hard to remain stupid

Connecting all of the networked devices to the one switch is best if you have enough available ports.

Assuming the switch has a high enough switching capacity (in the case of a 24 port 10/100 switch, it should be 4.8Gbps) there wont be any bottlenecks such as if you were to seperate it in to two seperate switches (the bottleneck would be the single 10/100 connection between the two switches). In fact, even if the switching capacity of the switch is limiting, you'd still be better to have everything on the one switch.

Now, I'm going to attempt to be a smart arse here, and one up that.

Get two managed switches that support Spanning Tree Protocol and port trunking and the like. Hook half your client PCs to one switch, and half to the other. Create a reasonabe size trunk between them (say, four connections). Take the four physical connections along different paths to maximise redundancy. Your server shoudl have two NICs. Plug one in to each of the switches, and set it up so both are active as essentially teh same conection, if possible (I am reasonably sure it is). If not, have the two switches on seperate VLANs, so both switches can talk to the server's NIC on their respective switch and then get the switches to route between teh two VLANs.

Or something like that >.>

Wise idea, although I like they way the squid thinks it would however make things harder to administer and the having least parts possible means the less likely there is of a disaster occuring.

And a also a big congrats on finshing your last assignment...


Edited by midbear: 27/11/2008 09:29:30 AM

---

Love is all fun and games until someone loses an eye or gets pregnant

LESS PARTYING MORE STUDYING.

And by studying I mean partying.

^_^