These days, most NIC's don't require one as they can cross over on the fly on their own...Mandy wrote:I
Though this seems a typo. In this setup, you MUST use a cross-over cable.
network through router for a dummy :)
I must get with the timesBob wrote:These days, most NIC's don't require one as they can cross over on the fly on their own...Mandy wrote:I
Though this seems a typo. In this setup, you MUST use a cross-over cable.
Us old phobies didn't even realise NICs had that option / auto-sensing ability Anyway, that implies either cable would work.
-
major.tom
- Macho Business Donkey Wrestler
- Posts: 1970
- Joined: Sun Jan 21, 2007 7:07 pm
- Location: BC, Canada
Me neither. That's pretty cool that newer NIC's can handle this automatically.Mandy wrote:I must get with the timesBob wrote:These days, most NIC's don't require one as they can cross over on the fly on their own...Mandy wrote:Though this seems a typo. In this setup, you MUST use a cross-over cable.
...as long as the NIC supports it.Anyway, that implies either cable would work.
My original error was the product of a murky memory. Nicely spotted.
So, is using MSN messenger to utilise remote desktop, and windows firewall to block internet use when not required, the easiest way to come as close as possible to what was asked?
Answers by email to overcomplicated@boilingwater.com !
Answers by email to overcomplicated@boilingwater.com !
-
major.tom
- Macho Business Donkey Wrestler
- Posts: 1970
- Joined: Sun Jan 21, 2007 7:07 pm
- Location: BC, Canada
I haven't used MSN messenger for this, but assuming it works, sure.
I was focusing more on the network topology that would prevent the 2nd computer from having access to the 'net. There are various tools you can use for remote desktop (eg. PC Anywhere, etc).
"Clustering" the two pc's to act as one (shared CPU & RAM) is much tougher nut to crack. You'd need some enterprise software like Microsoft Application Center for that.
I was focusing more on the network topology that would prevent the 2nd computer from having access to the 'net. There are various tools you can use for remote desktop (eg. PC Anywhere, etc).
"Clustering" the two pc's to act as one (shared CPU & RAM) is much tougher nut to crack. You'd need some enterprise software like Microsoft Application Center for that.
Last edited by major.tom on Thu Feb 07, 2008 8:32 am, edited 1 time in total.
-
Brown Sauce
- admin
- Posts: 1453
- Joined: Sun Jan 07, 2007 3:40 pm
-
major.tom
- Macho Business Donkey Wrestler
- Posts: 1970
- Joined: Sun Jan 21, 2007 7:07 pm
- Location: BC, Canada
...on the subject of Windows Firewall...
I don't have a very high opinion of it. a) it doesn't do outbound filtering, so if not being able to access the net is a requirement, it wouldn't do that. And b) unless you're running as a user with no admin privileges, pretty much any program will automatically open up a door on it and accept inbound connections from any computer that can reach it. If both computers are inside a router, no harm done, but there's no benefit either (unless you don't trust the ppl in your home).
Some routers might allow you to filter outbound traffic from a specific PC on your local network, but my Linksys doesn't. Maybe Netgear or Cisco. Or even Dlink.
I don't have a very high opinion of it. a) it doesn't do outbound filtering, so if not being able to access the net is a requirement, it wouldn't do that. And b) unless you're running as a user with no admin privileges, pretty much any program will automatically open up a door on it and accept inbound connections from any computer that can reach it. If both computers are inside a router, no harm done, but there's no benefit either (unless you don't trust the ppl in your home).
Some routers might allow you to filter outbound traffic from a specific PC on your local network, but my Linksys doesn't. Maybe Netgear or Cisco. Or even Dlink.