use netsh in batch file to configure crossover cable conn. 2 w7 computers SOLVED
On Thu, 7 Dec 2017 14:48:27 -0800, Mike S wrote:
On 12/7/2017 8:44 AM, Char Jackson wrote:
On Wed, 6 Dec 2017 21:42:35 -0800, Mike S wrote:
On 12/6/2017 8:48 PM, Mike S wrote:
I'm trying to use a batch file to configure the Local Area Connections
on 2 w7 computers so the user can xfer files using a crossover ethernet
FYI, if both PCs have Gigabit NICs, you don't need to use a crossover
cable. Any Ethernet cable will work. Sometimes that saves a trip to the
store, since most people don't have a crossover cable lying around.
Good to know, thanks.
This is for a guy who doesn't want to use a router, switch, or ad
hoc wifi connection. He is not comfortable with changing settings, so
I'm trying to make this as easy as possible for him. After I get that
working I'll see if a Homegroup is the easiest way for a non-savvy user
to transfer files. But right now this batch file which has two problems,
it won't configure the default gateway to be the same as the Local Area
Connection ipv4 address
Why on earth would you want the default gateway address to be the same
as the local address? What would that accomplish for you? If you don't
want a default gateway then simply don't configure one. Use the keyword
"none" in your command strings. When two hosts are on the same subnet,
like in your example, they don't need a default gateway to be able to
talk to each other.
Technically, they don't even need to be configured at all, in most
cases. Just connect the two PCs with any old Ethernet cable, assuming
both have GigE NICs, which most do these days, and both are configured
for DHCP, and let APIPA auto-assign addresses in the 169.254.0.0/16
Yes this works, thanks. I had thought the gateway had to be defined so
because the packets were sent there.
A gateway is only used when traffic is destined for a non-local subnet.
In your case, all of the traffic is confined to a single subnet, so a
gateway isn't required.