networking 2 computers query

theTinker

Hello Everyone.

Before i try set this up. I just wanted to check that my thinking is correct on this.

I have Computer A connected to a network with lots of security rules/shared network drives/active directory login etc.

If i connect a new computer B to computer A using the spare network port. Am i correct in my belief the computer A and B will have thier own private network between them? And that computer B can login to its windows installation, and share out a harddrive to Computer A privately?

Thanks for the information.

wexie

theTinker wrote: »

I have Computer A connected to a network with lots of security rules/shared network drives/active directory login etc.

If i connect a new computer B to computer A using the spare network port. Am i correct in my belief the computer A and B will have thier own private network between them? And that computer B can login to its windows installation, and share out a harddrive to Computer A privately?

Thanks for the information.

yes....potentially....but without more information it's rather hard to say.

Depending on the 'lots of security rules/shared network drives/active directory login etc' and whether or not these are yours to control/modify this might not be quite so straightforward.

theTinker

I dont know much about the rules on the network, just that I really need to avoid touching off it. However i have full admin rights over Computer A.

I was under the impression that the spare network port on the Computer A will be a totally new network when connected directly to Computer B, so if my thinking is correct, I shouldnt be interfering with the other network of Computer...or violating any rules.

Thanks for the response

Torqay

Should be possible. Use static IP addresses. You may need a "crossover" network cable, although this shouldn't be an issue with modern NICs.

wexie

Okay, without getting into too many details, what is it you're trying to achieve or want to do with / to machine A?

Like Torquay said you could just setup static IP addresses on both machines (different range) and then theoretically this should work.

wexie

theTinker wrote: »

...or violating any rules.

Let's just keep it at plausible deniability for the moment, but...the company I work for would, under no circumstances (officially) allow me to connect my own machine to the network. While there probably wouldn't be any rules specifically stating you couldn't use a direct connection between 2 machines I'm pretty sure they wouldn't be very happy with it.

theTinker

Its one of those fine lines im trying to walk.
I only need the idea to work for a proof of concept. then Im sure ill be told to immediately dissconnect it. After which ill already have the proof i need to make it a viable solution.

I forgot about the cross over cable being required. Thanks for that.

Ill use static IPs yes.

Great.

This really helps me out. Thanks very much for the confirmation.

One machine will be a xp box, the other a windows 7. Ill read up now on networking them, but im assuming there isnt any issues here?

wexie

Not really I guess, again depends on what you're trying to do, if it's just sharing a drive or so I don't think there should be any.

Also you might not need a crossover cable, most NIC's are autosensing these days.

Torqay

theTinker wrote: »

I forgot about the cross over cable being required.

Not really, Auto-MDIX is around for a long time.

yoyo

Torqay wrote: »

Not really, Auto-MDIX is around for a long time.

I'd say any NIC made in the last 7 years wouldn't worry about crossover and the likes. Actually using a crossover to connect my computer direct to the modem (was the largest bit of cat5 I had lying around), no issues whatsoever :P

Nick

theTinker

thanks guys, much appreciated

rolion

theTinker wrote: »

If i connect a new computer B to computer A using the spare network port.

Sorry...what is the reason of Computer A to have a second network port OR a second network card ?
I hope we are talking about network cards (back of the PC) and not second network points as in network wall socket's plate ?

theTinker

rolion wrote: »

Sorry...what is the reason of Computer A to have a second network port OR a second network card ?
I hope we are talking about network cards (back of the PC) and not second network points as in network wall socket's plate ?

Hey Rolion

Computer A just has 2 ethernet ports on the back of its mother board. My own PC at home has 2 ethernet ports too at home. I guess its cheap enough that its standard.

Nope not two network sockets on the wall.

Anyways. I had a followup question. Computer B will be a windows 7 machine. Computer A a windows xp. I assume its easy enough to forward all http(or just TCP/ip) requests through computer A. Is it just a matter of setting the Default Gateway on Computer B to computer As address, or do I have to set up some sort of port mapping forwarding?

Thanks for the help so far. Idea should work out well.

For any people interested. The reason for this is because I amnt allowed connect a windows 7 machine to network for a various barrage of BS reasons. So this maintains the current status quo configuration while allowing me to get a decent new machine....

rolion

Thanks for reply...!
Why don't you get a small 5 ports switch and connect both PCs to LAN ?

On XP box you have to enable IP routing or multi-homed bridging ! Check IP addressing and subnet mask !
Default Gateway you need only if is the LAN router to access WAN.

As you said there are reasons that will not allow connecting new PC to network,i advise to double check and/or to follow advise.

Is that those new BYOD (Bring Your Own Device) BS reasons ??!

theTinker

rolion wrote: »

Thanks for reply...!
Why don't you get a small 5 ports switch and connect both PCs to LAN ?

On XP box you have to enable IP routing or multi-homed bridging ! Check IP addressing and subnet mask !
Default Gateway you need only if is the LAN router to access WAN.

As you said there are reasons that will not allow connecting new PC to network,i advise to double check and/or to follow advise.

Is that those new BYOD (Bring Your Own Device) BS reasons ??!

More of a political BS reason. technical excuse is that the domain controller cant deal with Windows 7 logins etc, with it all the network resource sharing etc.
However Im hoping to set up a windows 7 box beside my PC which i can do all my work on, and route the little http traffic i need through the old box onto the network.
Its just a very small amount of HTTP traffic, if it works. Im hoping that my applications can send http traffic through my old pc while allowing me to do all my work on my new faster box...
The http traffic shouldnt have any issue on the network.

Im just a little uneducated in routing traffic through standard windows machines. Im hoping its straight forward.

wexie

How dya get on? Any luck?

Was thinking today if it's a problem you could always see if you could get a copy of VMware workstation (or ESXi even), stick it on the newer machine and get your IT gophers to pop the corporate XP build onto a VM?

rolion

i think he may have been let go ,due to the conflict with IT dept !?