Joedetic

Legit supplier...but was it legit staff and installation teams?

I've completed and passed all the components to CCNA 1 - 4. I missed on the voucher exam because of various reasons so it looks like I'm not going to be able to afford to complete the actual qualification any time soon (can't afford it). Sods law really. At least I didn't have to pay for it (well...it's a part of my university course).

I guess I'm not young enough...I've seen it before. Damnnit with the getting older!

lol Nice and simple?

Best Tech Under 21 instead of 18 then you're looking like something I might have a chance at winning lol. I just miss the 18 y/o one by almost two years

OK I'll start with a bit of a leading question. VoIP or IP Telephony? I've had experience using both SIP systems and Skinny as well as a bit of a play with a standard digital PBX which has nothing to do with IPT or VoIP. The IP Telephony option is a lot more involved and would involve VLANs and Cisco kit (the way I've done it anyway). Sip can be a lot more flexible and cheaper to implement. With regards to wireless phones. I know Cisco do some (we've got some in the lab at uni), they're very nice little units indeed.

Yesterday I was mostly getting my hair cut, drinking pimms and sorting things with the DVLA and endsleigh. Today I will be mostly failing and Advanced Routing practical test (CCNP 1) and wondering whether I have broken my finger smashing up a hard drive with a big rock for a housemate.

How does this nessus plugin work. I have nessus installed on my work laptop but as far as I've used it in the past it's a port / vulnerability scanner.

Ubuntu for first time users is great....if you wanted to dive in at the deep end with something Unix-based but not Linux....take a looksee into FreeBSD....not so great for desktops in my opinion but it's brilliant for servers. There's a few books on Amazon that are great. That's how I got into FreeBSD.

If you're using some horrid old hubs or unmanaged switches that don't support vlanning then just re-patch the two networks into different switches. It could also prove quicker if you're not familiar with the process. VLANs and physical separation are the two ways that I can think of to reduce your broadcast domain to cope with your problem. Short of setting up two scopes on the dhcp server and using mac reservations but this kind of defeats the point i suspect (that and I don't know if that'll work??)

Heh...nearest chippy to where dad lives is a 10 minute drive in his XKR (and that's flooring it!)

@tech_guy if only....my hangovers clear quite quickly but two pints of ale aren't going to cause a hangover

I've got a couple of mates from uni that live in Hastings that mentioned the beer festival. I hope they do continue it because I wanted to go lol.

Friday was Alton Towers with mates from Uni. Friday night my dad came and got me and I spent the weekend at his. Walked the dogs, took two youngest of the 4 to the pub and sat in the beer garden and had dinner. Sunday felt like crap...had some 24hr bug thing that felt like condensed man-flu Went to a mate's bbq in the evening whilst everyone was sat around in shorts i was wearing jeans and two hoodies and then had to go and have a lie down. Seems to be gone today though.

*cough* "Lock the taskbar, lock the taskbar" *cough*

@tech_guy I love that track.

Yeah, the only reason I mentioned the frame relay was because it cropped up on an exam about remote access networks this morning and I've had my fill of it But yes...as both I and torledo have said, if it's managed get BT to sort it. It may even be their DCE equipment that's dropping the line and your serial interface (if that's what it's using??) is not picking it back up again. (Just reading your post that appeared after I hit post...LES 10 that's ethernet into the router right? Flow control issues LAN side wouldn't drop your internet connection I wouldn't have thought. If you can get a machine and plug it in direct to the router LAN ethernet port via crossover and see what happens and if you can get the connection drop it isn't your dlink kit)

I've got experience of them in a lab environment. What you should be doing is setting up the syslog stuff and logging out to a log server to see what's going on for a start in my opinion. If the router was supplied by BT and they configured it then you should be getting in touch with them to come and troubleshoot it for you. What kind of leased line have you got? It'd be useful to know. (If you say you've got frame relay I'm going to run the other way screaming...just so you know )

Question stands that why don't you just copy the way you're doing it in your other school??? Or at least take how you're doing it there and modify it to this situation :S

If you're not using any configs on the two switches just make sure they're clear (asside from the usual passwords and secrets etc) and then just plug a crossover in between the two....I think you're over complicating things. It doesn't even have to be a crossover really because those switches will negotiate a link.

My phone got dropped off a bench outside the pub a few weeks back (ok it's not an iPAQ...but it was expensive)....luckily it got nicked from the swimming baths last week (unluckily with my wallet and keys, dry clothes and a pair of glasses). I've got a nice new scratch free one on insurance now

Just don't forward the necessary port then. (3389 iirc)

To be brutally honest if you want to actually understand fully what you're doing to your switches CLI is the best way to go as Torledo mentioned. The cisco training materials teach CLI configs as far as they can. For devices like the APs (some of which don't do CLI very well so I'm told), PIXs and ASAs GUI is more acceptable. PIX and ASA are most easily configured using ASDM in my opinion. The CLI on finesse is awfully restrictive imho. They should have kept the same command structure as they use in IOS instead of buggering about and messing it up.

I just don't have the time. If I'm waiting for something to install or compile I might occasionally run my finger along the bit in between the F keys and the numbers....then wonder where to wipe the dust from the end of my finger for 5 minutes. I normally go with the carpet for some strange reason.

Check your IOS versions on each switch and you'll probably find that they are running different versions. Then you'll need to check the memory on the switches. Check that the one with the naff IOS on to see if it's got enough space to put the decent one on using tftp. What you'll want to do before you do that is to backup your startup-config and check with Cisco about the licensing implications of this because I'm not sure you're "allowed" to do this. If, however, you're referring to the http gui...shame on you You'll need to look at the versions of IOS /and/ the http interface.