Subj : Re: Alternative solution - was [Re: Manually setting a STATIC IP in To : All From : rowlett@cloud85.net Date : Fri Jan 18 2019 10:56 am Path: eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!1 ..eu.feeder.erje.net!feeder.erje.net!2.us.feeder.erje.net!weretis.net!feeder6.ne ws.weretis.net!feeder.usenetexpress.com!feeder1.iad1.usenetexpress.com!216.166. 98.84.MISMATCH!border1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dc a1.giganews.com!buffer2.nntp.dca1.giganews.com!nntp.supernews.com!news.supernew s.com.POSTED!not-for-mail NNTP-Posting-Date: Wed, 18 Jan 2017 10:56:20 -0600 Subject: Re: Alternative solution - was [Re: Manually setting a STATIC IP in WinXPPro] Newsgroups: microsoft.public.windowsxp.help_and_support References: <587f8750$0$21525$e4fe514c@news.xs4all.nl> From: Richard Owlett Date: Wed, 18 Jan 2017 10:56:17 -0600 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 MIME-Version: 1.0 In-Reply-To: <587f8750$0$21525$e4fe514c@news.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: Lines: 68 X-Trace: sv3-UxC2HsS7YPTtwNUKWIEKi+i1b85ACpg85R4ZkyH0aVinaNt9xV83UV4L59auaRF6RSpN41pD4hZ mAyH!lf8vrHU76eqT3erODlug5yeeDU/tegwL4jJxgRdb54QxviXYbAZQk6zqOKzSYh+MfoUa/T0yWp RC!2Zx3CNcYpA== X-Complaints-To: www.supernews.com/docs/abuse.html X-DMCA-Complaints-To: www.supernews.com/docs/dmca.html X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 3725 Xref: news.eternal-september.org microsoft.public.windowsxp.help_and_support:31892 On 1/18/2017 9:23 AM, R.Wieser wrote: > Richard, > >> The minimal network was being pursued as it was a close as >> I *HAD THOUGHT* I could come to a "null modem cable". > > Thats the "cross over" cable I mentioned* :-) > > *although a null-modem cable normally includes cross-over, it does need to. *NO* A "cross over" cable connects two Ethernet ports. https://en.wikipedia.org/wiki/Medium-dependent_interface#Auto_MDI-X A "null-modem" connects two DTE or two DCE together. https://en.wikipedia.org/wiki/Data_circuit-terminating_equipment https://en.wikipedia.org/wiki/Data_terminal_equipment https://en.wikipedia.org/wiki/Null_modem IOW connect COM ports of two computers to each other. P.S. I've been using null modems for >50 years ;} Ethernet is only ~30 years old. https://en.wikipedia.org/wiki/Ethernet > > But its still a good idea to first connect to a known-to-be-good device (the > modem or smart switch (or anything else with a web-accessible setup) I > mentioned) so that you can see your fixed IP actually works (on both > 'puters), _before_ you try that cross-over cable (I'm not sure you realize, > but now you've introduced a _third_ location that could give you troubles > with setting up such a 'puter-to-'puter connection). > > Regards, > Rudy Wieser > > > -- Origional question. > Richard Owlett schreef in berichtnieuws > LZydneiMicXqHOLFnZ2dnUU7-XnNnZ2d@supernews.com... >> On 1/16/2017 7:47 AM, Richard Owlett wrote: >>> I have two Lenovo laptops. One running WinXP Pro. The other runs >>> Linux. >>> I wish to create a minimal network. It will consist of only those >>> two machines. >>> Neither will have any internet connectivity. >>> >>> I've found a number of web references to setting static IP >>> addresses on Windows machines. >>> *HOWEVER* assume internet connectivity by one/both machines. >>> >>> Can anyone point me to any documentation EXPLICITLY covering my >>> {admittedly} peculiar requirement. >>> >>> TIA >> >> The minimal network was being pursued as it was a close as I *HAD >> THOUGHT* I could come to a "null modem cable". >> A USB implementation is available - >> http://www.mouser.com/ds/2/163/DS_USBNMC-5030.pdf . >> I'll check local suppliers. >> Will also continue pursuing the LAN solution for its educational >> value. > > > --- Platinum Xpress/Win/WINServer v3.1 * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013) .