question on static addresses

  • Thread starter Thread starter Sam
  • Start date Start date
S

Sam

I want to network two computers. The problem is that my
ISP doesn't provide static ip addresses. I beleive that
in order to connect two machines without a device like a
hub, I need a crossover cable and manually assigned ip
addresses. Any solutions?
 
"Sam" said:
I want to network two computers. The problem is that my
ISP doesn't provide static ip addresses. I beleive that
in order to connect two machines without a device like a
hub, I need a crossover cable and manually assigned ip
addresses. Any solutions?

There's no need for manually assigned IP addresses, Sam. Here are
some possible solutions, in order, from best to worst. They all give
Internet access to both computers and let the computers share files
and printers with each other, while protecting them against access by
other Internet users:

1. Get a broadband router, connect your ISP connection to its WAN
(Internet) port, and connect the computers to its LAN ports. The
router will receive a dynamic public IP address from your ISP, and
your computers will receive dynamic private IP addresses from the
router. The router's built-in firewall function will protect them
from access by other Internet users.

2. Install two network cards in one of the computers. Connect your
ISP connection to one of them and connect the other computer to the
other one using a crossover cable. Enable Internet Connection Sharing
on the ISP connection, and enable XP's built-in Internet Connection
Firewall on that connection to protect your computers from access by
other Internet users. These web pages have details:

Windows XP Internet Connection Sharing
http://www.practicallynetworked.com/sharing/xp_ics

Windows XP Internet Connection Firewall
http://www.practicallynetworked.com/sharing/xp/ic_firewall.htm

3. Get two dynamic IP addresses from your ISP. Connect the ISP
connection to the uplink port of a hub or switch, and connect the
computers to regular ports. Because other Internet users might be
able to access your computers using the TCP/IP protocol, un-bind
sharing from TCP/IP, and install the NWLink IPX/SPX protocol for file
sharing. This web page has details:

Windows XP Network Protocols
http://www.practicallynetworked.com/sharing/xp/network_protocols.htm
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
"Sam" said:
Thanks for the reply Steve.

The reason why I asked was because I have read
practicallynetworked's "Networking Two PCs via a
Crossover cable" and it said that I need manually
assigned ip addresses. You can read all about it and why
I was lead to beleive it.

Networking Two PCs Via a Crossover Cable
http://www.practicallynetworked.com/qa/qa20030213.shtml

What the article says will work, but it doesn't give the full story.

If either of the computers runs Windows 95 or Windows NT, both
computers need static IP addresses.

If both computers run Windows 98, 98SE, Me, 2000, or XP, static IP
addresses aren't needed. Those Windows versions can assign themselves
dynamic IP addresses without a DHCP server on the network.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
Steve Winograd said:
If both computers run Windows 98, 98SE, Me, 2000, or XP, static IP
addresses aren't needed. Those Windows versions can assign themselves
dynamic IP addresses without a DHCP server on the network.
--

Are you speaking of the auto-configuration IP addresses?
(BTW, are these analogous to link-local addresses in IPv6?)

Is Windows smart enough to generate non-overlapping
auto-configuration addresses for all interfaces on a given system?
That is, is it smart enough to make sure all the ones it
generates for a given system are on different subnets (eg, one
for the wireless, one for the wired, one for the firewire, etc,
for however many network connections it winds up generating them).
 
Back
Top