|
windows
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Networking with 2 computers2 computers No DHCP server No Router No Switch I know the faster way to make two computers to talk to each other is using a cross-over cable and assign static IP address on each one of them. Somone told me there is another way to do it, and I just want to confirm this with the experts here. He said two computers can talk to each other just by computer_name, without any IP address. My question: How reliable is this? PROS & CONS? All the comments are welcome. Thanks J. =?Utf-8?B?Sm9obm55?= <Joh***@discussions.microsoft.com> wrote in
Show quoteHide quote news:581252BE-F1F1-4693-89B8-3BEC392842F7@microsoft.com: Well, technically, you will have an IP address. If you connect two > Lab environment: > 2 computers > No DHCP server > No Router > No Switch > > I know the faster way to make two computers to talk to each other > is using a cross-over cable and assign static IP address on each > one of them. > > Somone told me there is another way to do it, and I just want to > confirm this with the experts here. He said two computers can talk > to each other just by computer_name, without any IP address. > > My question: How reliable is this? computers configured for DHCP together with a cross-cable and wait a while, each computer will give the "Little or no connectivity" error message and then automatically assign themselves a random 169.254.x.x (IIRC) address. (This assumes that in the network control panel for your NIC, under TCP/IP Properties "Alternate Configuration" Tab you have the "Obtain an IP address automatically" checked -- which should be default), Once this happens, they can freely communicate using this ad-hoc IP address. Microsoft networking establishes connectivity using Names and Broadcasts, so as long as there are no firewalls in place and neither machine is a P-Type node, you are good to go. -- John Hi John,
Thanks for responding, I tried this without setting any thing in the TCP/IP preperties, just put a cross-over cable between these two computers, sometime the connection cannot be reach. It does not establish the communication everytime I restart these two comptuers. If I shutdown both of them, then I turn on the PC-1 and wait until it gets to the desktop, then I power on the PC-2, the application we are running does not always work (no communication). How reliable is this type of setting vs. assign an IP address on each one of them, and then add the IP and computername in the HOSTS file, so the computername can be always reached. J Show quoteHide quote "John Wunderlich" wrote: > =?Utf-8?B?Sm9obm55?= <Joh***@discussions.microsoft.com> wrote in > news:581252BE-F1F1-4693-89B8-3BEC392842F7@microsoft.com: > > > Lab environment: > > 2 computers > > No DHCP server > > No Router > > No Switch > > > > I know the faster way to make two computers to talk to each other > > is using a cross-over cable and assign static IP address on each > > one of them. > > > > Somone told me there is another way to do it, and I just want to > > confirm this with the experts here. He said two computers can talk > > to each other just by computer_name, without any IP address. > > > > My question: How reliable is this? > > Well, technically, you will have an IP address. If you connect two > computers configured for DHCP together with a cross-cable and wait a > while, each computer will give the "Little or no connectivity" error > message and then automatically assign themselves a random 169.254.x.x > (IIRC) address. (This assumes that in the network control panel for > your NIC, under TCP/IP Properties "Alternate Configuration" Tab you > have the "Obtain an IP address automatically" checked -- which should > be default), Once this happens, they can freely communicate using > this ad-hoc IP address. Microsoft networking establishes connectivity > using Names and Broadcasts, so as long as there are no firewalls in > place and neither machine is a P-Type node, you are good to go. > > > -- John > =?Utf-8?B?Sm9obm55?= <Joh***@discussions.microsoft.com> wrote in
Show quoteHide quote news:45272056-F5E7-46AD-84AA-5410756DCA9E@microsoft.com: Besides the IP Address negotiation, there is also line speed, duplex, > > "John Wunderlich" wrote: > >> =?Utf-8?B?Sm9obm55?= <Joh***@discussions.microsoft.com> wrote in >> news:581252BE-F1F1-4693-89B8-3BEC392842F7@microsoft.com: >> >>> Lab environment: >>> 2 computers >>> No DHCP server >>> No Router >>> No Switch >>> >>> I know the faster way to make two computers to talk to each >>> other is using a cross-over cable and assign static IP address >>> on each one of them. >>> >>> Somone told me there is another way to do it, and I just want to >>> confirm this with the experts here. He said two computers can >>> talk to each other just by computer_name, without any IP >>> address. >>> >>> My question: How reliable is this? >> >> Well, technically, you will have an IP address. If you connect >> two computers configured for DHCP together with a cross-cable and >> wait a while, each computer will give the "Little or no >> connectivity" error message and then automatically assign >> themselves a random 169.254.x.x (IIRC) address. (This assumes >> that in the network control panel for your NIC, under TCP/IP >> Properties "Alternate Configuration" Tab you have the "Obtain an >> IP address automatically" checked -- which should be default), >> Once this happens, they can freely communicate using this ad-hoc >> IP address. Microsoft networking establishes connectivity using >> Names and Broadcasts, so as long as there are no firewalls in >> place and neither machine is a P-Type node, you are good to go. >> >> >> -- John >> > > Hi John, > > Thanks for responding, I tried this without setting any thing in > the TCP/IP preperties, just put a cross-over cable between these > two computers, sometime the connection cannot be reach. It does > not establish the communication everytime I restart these two > comptuers. If I shutdown both of them, then I turn on the PC-1 and > wait until it gets to the desktop, then I power on the PC-2, the > application we are running does not always work (no > communication). How reliable is this type of setting vs. assign an > IP address on each one of them, and then add the IP and > computername in the HOSTS file, so the computername can be always > reached. > > J and signal direction negotiation. Since both ends of the line are trying to detect speed & duplex simultaneously, it is not unusual for each end to come up with a different answer. (A router/switch is fixed so that only the computer end is negotiating -- but with two computers, both ends are simultaneously negotiating). If you go into the Device manager (Start->Run->"devmgmt.msc") and double-click on your NIC card and go to the "Advanced" tab, there should be an entry for Speed & Duplex. This is usually set to "Auto". Manually setting this to the same speed at both ends and "Full Duplex" instead of "Auto" should improve initial connectivity problems. Newer NICs also self-sense direction (i.e. a regular cable may work instead of a cross cable). I haven't found a manual setting for this. Once connection is established, Windows networking should work just as well either way. If you are using an application like FTP to transfer files, then the Fixed IP method takes the randomness of the IP address out of the mix but otherwise should work equally well. HTH, John John,
Is this what they called "APIPA"? What is the difference between APIPA vs. Ad-Hoc? J. Show quoteHide quote "John Wunderlich" wrote: > =?Utf-8?B?Sm9obm55?= <Joh***@discussions.microsoft.com> wrote in > news:45272056-F5E7-46AD-84AA-5410756DCA9E@microsoft.com: > > > > > "John Wunderlich" wrote: > > > >> =?Utf-8?B?Sm9obm55?= <Joh***@discussions.microsoft.com> wrote in > >> news:581252BE-F1F1-4693-89B8-3BEC392842F7@microsoft.com: > >> > >>> Lab environment: > >>> 2 computers > >>> No DHCP server > >>> No Router > >>> No Switch > >>> > >>> I know the faster way to make two computers to talk to each > >>> other is using a cross-over cable and assign static IP address > >>> on each one of them. > >>> > >>> Somone told me there is another way to do it, and I just want to > >>> confirm this with the experts here. He said two computers can > >>> talk to each other just by computer_name, without any IP > >>> address. > >>> > >>> My question: How reliable is this? > >> > >> Well, technically, you will have an IP address. If you connect > >> two computers configured for DHCP together with a cross-cable and > >> wait a while, each computer will give the "Little or no > >> connectivity" error message and then automatically assign > >> themselves a random 169.254.x.x (IIRC) address. (This assumes > >> that in the network control panel for your NIC, under TCP/IP > >> Properties "Alternate Configuration" Tab you have the "Obtain an > >> IP address automatically" checked -- which should be default), > >> Once this happens, they can freely communicate using this ad-hoc > >> IP address. Microsoft networking establishes connectivity using > >> Names and Broadcasts, so as long as there are no firewalls in > >> place and neither machine is a P-Type node, you are good to go. > >> > >> > >> -- John > >> > > > > > Hi John, > > > > Thanks for responding, I tried this without setting any thing in > > the TCP/IP preperties, just put a cross-over cable between these > > two computers, sometime the connection cannot be reach. It does > > not establish the communication everytime I restart these two > > comptuers. If I shutdown both of them, then I turn on the PC-1 and > > wait until it gets to the desktop, then I power on the PC-2, the > > application we are running does not always work (no > > communication). How reliable is this type of setting vs. assign an > > IP address on each one of them, and then add the IP and > > computername in the HOSTS file, so the computername can be always > > reached. > > > > J > > Besides the IP Address negotiation, there is also line speed, duplex, > and signal direction negotiation. Since both ends of the line are > trying to detect speed & duplex simultaneously, it is not unusual for > each end to come up with a different answer. (A router/switch is fixed > so that only the computer end is negotiating -- but with two computers, > both ends are simultaneously negotiating). If you go into the Device > manager (Start->Run->"devmgmt.msc") and double-click on your NIC card > and go to the "Advanced" tab, there should be an entry for Speed & > Duplex. This is usually set to "Auto". Manually setting this to the > same speed at both ends and "Full Duplex" instead of "Auto" should > improve initial connectivity problems. Newer NICs also self-sense > direction (i.e. a regular cable may work instead of a cross cable). I > haven't found a manual setting for this. > > Once connection is established, Windows networking should work just as > well either way. If you are using an application like FTP to transfer > files, then the Fixed IP method takes the randomness of the IP address > out of the mix but otherwise should work equally well. > > HTH, > John > =?Utf-8?B?Sm9obm55?= <Joh***@discussions.microsoft.com> wrote in
Show quoteHide quote news:896780E3-733F-4CE8-8297-6545CE562F75@microsoft.com: Yes. This is APIPA> "John Wunderlich" wrote: > >> =?Utf-8?B?Sm9obm55?= <Joh***@discussions.microsoft.com> wrote in >> news:45272056-F5E7-46AD-84AA-5410756DCA9E@microsoft.com: >> >>> >>> "John Wunderlich" wrote: >>> >>>> =?Utf-8?B?Sm9obm55?= <Joh***@discussions.microsoft.com> wrote >>>> in news:581252BE-F1F1-4693-89B8-3BEC392842F7@microsoft.com: >>>> >>>>> Lab environment: >>>>> 2 computers >>>>> No DHCP server >>>>> No Router >>>>> No Switch >>>>> >>>>> I know the faster way to make two computers to talk to each >>>>> other is using a cross-over cable and assign static IP address >>>>> on each one of them. >>>>> >>>>> Somone told me there is another way to do it, and I just want >>>>> to confirm this with the experts here. He said two computers >>>>> can talk to each other just by computer_name, without any IP >>>>> address. >>>>> >>>>> My question: How reliable is this? >>>> >>>> Well, technically, you will have an IP address. If you connect >>>> two computers configured for DHCP together with a cross-cable >>>> and wait a while, each computer will give the "Little or no >>>> connectivity" error message and then automatically assign >>>> themselves a random 169.254.x.x (IIRC) address. (This assumes >>>> that in the network control panel for your NIC, under TCP/IP >>>> Properties "Alternate Configuration" Tab you have the "Obtain >>>> an IP address automatically" checked -- which should be >>>> default), Once this happens, they can freely communicate using >>>> this ad-hoc IP address. Microsoft networking establishes >>>> connectivity using Names and Broadcasts, so as long as there >>>> are no firewalls in place and neither machine is a P-Type node, >>>> you are good to go. >>>> >>>> >>>> -- John >>>> >>> >> >>> Hi John, >>> >>> Thanks for responding, I tried this without setting any thing in >>> the TCP/IP preperties, just put a cross-over cable between these >>> two computers, sometime the connection cannot be reach. It does >>> not establish the communication everytime I restart these two >>> comptuers. If I shutdown both of them, then I turn on the PC-1 >>> and wait until it gets to the desktop, then I power on the PC-2, >>> the application we are running does not always work (no >>> communication). How reliable is this type of setting vs. assign >>> an IP address on each one of them, and then add the IP and >>> computername in the HOSTS file, so the computername can be >>> always reached. >>> >>> J >> >> Besides the IP Address negotiation, there is also line speed, >> duplex, and signal direction negotiation. Since both ends of the >> line are trying to detect speed & duplex simultaneously, it is >> not unusual for each end to come up with a different answer. (A >> router/switch is fixed so that only the computer end is >> negotiating -- but with two computers, both ends are >> simultaneously negotiating). If you go into the Device manager >> (Start->Run->"devmgmt.msc") and double-click on your NIC card >> and go to the "Advanced" tab, there should be an entry for Speed >> & Duplex. This is usually set to "Auto". Manually setting this >> to the same speed at both ends and "Full Duplex" instead of >> "Auto" should improve initial connectivity problems. Newer NICs >> also self-sense direction (i.e. a regular cable may work instead >> of a cross cable). I haven't found a manual setting for this. >> >> Once connection is established, Windows networking should work >> just as well either way. If you are using an application like >> FTP to transfer files, then the Fixed IP method takes the >> randomness of the IP address out of the mix but otherwise should >> work equally well. >> >> HTH, >> John >> > John, > > Is this what they called "APIPA"? > What is the difference between APIPA vs. Ad-Hoc? > > J. <http://msdn.microsoft.com/en-us/library/aa505918.aspx> "Ad-Hoc", as far as I know, is a method for two wireless computers to connect directly to each other without use of an Access Point or Wireless Router. It may use APIPA to assign an IP address. <http://en.wikipedia.org/wiki/Ad-hoc_network> My use of the word "ad-hoc" was the standard English language definition. -- John John,
Is APIPA reliable, is this a good option to be used for business? J. Show quoteHide quote "John Wunderlich" wrote: > =?Utf-8?B?Sm9obm55?= <Joh***@discussions.microsoft.com> wrote in > news:896780E3-733F-4CE8-8297-6545CE562F75@microsoft.com: > > > "John Wunderlich" wrote: > > > >> =?Utf-8?B?Sm9obm55?= <Joh***@discussions.microsoft.com> wrote in > >> news:45272056-F5E7-46AD-84AA-5410756DCA9E@microsoft.com: > >> > >>> > >>> "John Wunderlich" wrote: > >>> > >>>> =?Utf-8?B?Sm9obm55?= <Joh***@discussions.microsoft.com> wrote > >>>> in news:581252BE-F1F1-4693-89B8-3BEC392842F7@microsoft.com: > >>>> > >>>>> Lab environment: > >>>>> 2 computers > >>>>> No DHCP server > >>>>> No Router > >>>>> No Switch > >>>>> > >>>>> I know the faster way to make two computers to talk to each > >>>>> other is using a cross-over cable and assign static IP address > >>>>> on each one of them. > >>>>> > >>>>> Somone told me there is another way to do it, and I just want > >>>>> to confirm this with the experts here. He said two computers > >>>>> can talk to each other just by computer_name, without any IP > >>>>> address. > >>>>> > >>>>> My question: How reliable is this? > >>>> > >>>> Well, technically, you will have an IP address. If you connect > >>>> two computers configured for DHCP together with a cross-cable > >>>> and wait a while, each computer will give the "Little or no > >>>> connectivity" error message and then automatically assign > >>>> themselves a random 169.254.x.x (IIRC) address. (This assumes > >>>> that in the network control panel for your NIC, under TCP/IP > >>>> Properties "Alternate Configuration" Tab you have the "Obtain > >>>> an IP address automatically" checked -- which should be > >>>> default), Once this happens, they can freely communicate using > >>>> this ad-hoc IP address. Microsoft networking establishes > >>>> connectivity using Names and Broadcasts, so as long as there > >>>> are no firewalls in place and neither machine is a P-Type node, > >>>> you are good to go. > >>>> > >>>> > >>>> -- John > >>>> > >>> > >> > >>> Hi John, > >>> > >>> Thanks for responding, I tried this without setting any thing in > >>> the TCP/IP preperties, just put a cross-over cable between these > >>> two computers, sometime the connection cannot be reach. It does > >>> not establish the communication everytime I restart these two > >>> comptuers. If I shutdown both of them, then I turn on the PC-1 > >>> and wait until it gets to the desktop, then I power on the PC-2, > >>> the application we are running does not always work (no > >>> communication). How reliable is this type of setting vs. assign > >>> an IP address on each one of them, and then add the IP and > >>> computername in the HOSTS file, so the computername can be > >>> always reached. > >>> > >>> J > >> > >> Besides the IP Address negotiation, there is also line speed, > >> duplex, and signal direction negotiation. Since both ends of the > >> line are trying to detect speed & duplex simultaneously, it is > >> not unusual for each end to come up with a different answer. (A > >> router/switch is fixed so that only the computer end is > >> negotiating -- but with two computers, both ends are > >> simultaneously negotiating). If you go into the Device manager > >> (Start->Run->"devmgmt.msc") and double-click on your NIC card > >> and go to the "Advanced" tab, there should be an entry for Speed > >> & Duplex. This is usually set to "Auto". Manually setting this > >> to the same speed at both ends and "Full Duplex" instead of > >> "Auto" should improve initial connectivity problems. Newer NICs > >> also self-sense direction (i.e. a regular cable may work instead > >> of a cross cable). I haven't found a manual setting for this. > >> > >> Once connection is established, Windows networking should work > >> just as well either way. If you are using an application like > >> FTP to transfer files, then the Fixed IP method takes the > >> randomness of the IP address out of the mix but otherwise should > >> work equally well. > >> > >> HTH, > >> John > >> > > > > John, > > > > Is this what they called "APIPA"? > > What is the difference between APIPA vs. Ad-Hoc? > > > > J. > > Yes. This is APIPA > <http://msdn.microsoft.com/en-us/library/aa505918.aspx> > > "Ad-Hoc", as far as I know, is a method for two wireless computers to > connect directly to each other without use of an Access Point or > Wireless Router. It may use APIPA to assign an IP address. > <http://en.wikipedia.org/wiki/Ad-hoc_network> > > My use of the word "ad-hoc" was the standard English language > definition. > -- John > > > =?Utf-8?B?Sm9obm55?= <Joh***@discussions.microsoft.com> wrote in
news:57819DF3-2C5F-4C23-B78C-3EB8517B8156@microsoft.com: I have found it (APIPA) to be fairly reliable in that when a DHCP > John, > > Is APIPA reliable, is this a good option to be used for business? > > J. > server is not available the computers will assign themselves an APIPA address. Other factors such as negotiating speed / duplex may not be as reliable depending on the hardware used. -- John You can set up an ad-hoc wireless network. The "Someone" was not
politically correct - in the "olden days" (pre XP) computer names were resolved by "NetBIOS" (IP address resolution). Much simpler to assign IP address via TCP/IP properties. AJR,
Can "Ad-Hoc" work with wired network (XP to XP)? J. Show quoteHide quote "AJR" wrote: > You can set up an ad-hoc wireless network. The "Someone" was not > politically correct - in the "olden days" (pre XP) computer names were > resolved by "NetBIOS" (IP address resolution). Much simpler to assign IP > address via TCP/IP properties. > > > Hi
It might be that "Someone" meant to run the two with NetBEUI and crossover cable. NetBEUI does not work with IPs but with computers names. If the computers have any other Network/Internet connection, then you need TCP/IP anyway. Configuring two computers with static IPs take few minutes. In any case if you want to play with Win XP and NetBEUI. http://www.ezlan.net/netbeui.html Jack (MS, MVP-Networking) Show quoteHide quote "Johnny" <Joh***@discussions.microsoft.com> wrote in message news:581252BE-F1F1-4693-89B8-3BEC392842F7@microsoft.com... > Lab environment: > 2 computers > No DHCP server > No Router > No Switch > > I know the faster way to make two computers to talk to each other is using > a > cross-over cable and assign static IP address on each one of them. > > Somone told me there is another way to do it, and I just want to confirm > this with the experts here. He said two computers can talk to each other > just > by computer_name, without any IP address. > > My question: How reliable is this? > > PROS & CONS? > > All the comments are welcome. > > Thanks > > J. > hi Jack,
I used to configure NetBEUI back in the old days for DOS network/Win95/98/NT/XP. But now we don't use NetBEUI any more, this person is saying to use "Link-Local Address" I guess it's the same as APIPA to communicate these two computers. I just don't understand why he preferred to use APIPA instead of conventional IP for network. How reliable is this APIPA? J. Show quoteHide quote "Jack-MVP" wrote: > Hi > It might be that "Someone" meant to run the two with NetBEUI and crossover > cable. > NetBEUI does not work with IPs but with computers names. > If the computers have any other Network/Internet connection, then you need > TCP/IP anyway. > Configuring two computers with static IPs take few minutes. > In any case if you want to play with Win XP and NetBEUI. > http://www.ezlan.net/netbeui.html > Jack (MS, MVP-Networking) > > "Johnny" <Joh***@discussions.microsoft.com> wrote in message > news:581252BE-F1F1-4693-89B8-3BEC392842F7@microsoft.com... > > Lab environment: > > 2 computers > > No DHCP server > > No Router > > No Switch > > > > I know the faster way to make two computers to talk to each other is using > > a > > cross-over cable and assign static IP address on each one of them. > > > > Somone told me there is another way to do it, and I just want to confirm > > this with the experts here. He said two computers can talk to each other > > just > > by computer_name, without any IP address. > > > > My question: How reliable is this? > > > > PROS & CONS? > > > > All the comments are welcome. > > > > Thanks > > > > J. > > > > Hi
The world is full of mysteries, and this might be one of them. ;). I have No clue what, and why. If "SomeOne" can not explain clearly, and you do not have any unusual specific needs, then forget about it. Jack (MS, MVP-Networking) Show quoteHide quote "Johnny" <Joh***@discussions.microsoft.com> wrote in message news:8E403762-190D-4F40-974D-6B71AEAB3760@microsoft.com... > hi Jack, > > I used to configure NetBEUI back in the old days for DOS > network/Win95/98/NT/XP. > But now we don't use NetBEUI any more, this person is saying to use > "Link-Local Address" I guess it's the same as APIPA to communicate these > two > computers. > I just don't understand why he preferred to use APIPA instead of > conventional IP for network. How reliable is this APIPA? > > J. > > "Jack-MVP" wrote: > >> Hi >> It might be that "Someone" meant to run the two with NetBEUI and >> crossover >> cable. >> NetBEUI does not work with IPs but with computers names. >> If the computers have any other Network/Internet connection, then you >> need >> TCP/IP anyway. >> Configuring two computers with static IPs take few minutes. >> In any case if you want to play with Win XP and NetBEUI. >> http://www.ezlan.net/netbeui.html >> Jack (MS, MVP-Networking) >> >> "Johnny" <Joh***@discussions.microsoft.com> wrote in message >> news:581252BE-F1F1-4693-89B8-3BEC392842F7@microsoft.com... >> > Lab environment: >> > 2 computers >> > No DHCP server >> > No Router >> > No Switch >> > >> > I know the faster way to make two computers to talk to each other is >> > using >> > a >> > cross-over cable and assign static IP address on each one of them. >> > >> > Somone told me there is another way to do it, and I just want to >> > confirm >> > this with the experts here. He said two computers can talk to each >> > other >> > just >> > by computer_name, without any IP address. >> > >> > My question: How reliable is this? >> > >> > PROS & CONS? >> > >> > All the comments are welcome. >> > >> > Thanks >> > >> > J. >> > >> >> Needs: commmunicate by name between these 2 computers, via cross-over or
switch. Show quoteHide quote "Jack-MVP" wrote: > Hi > The world is full of mysteries, and this might be one of them. ;). > I have No clue what, and why. If "SomeOne" can not explain clearly, and you > do not have any unusual specific needs, then forget about it. > Jack (MS, MVP-Networking) > > "Johnny" <Joh***@discussions.microsoft.com> wrote in message > news:8E403762-190D-4F40-974D-6B71AEAB3760@microsoft.com... > > hi Jack, > > > > I used to configure NetBEUI back in the old days for DOS > > network/Win95/98/NT/XP. > > But now we don't use NetBEUI any more, this person is saying to use > > "Link-Local Address" I guess it's the same as APIPA to communicate these > > two > > computers. > > I just don't understand why he preferred to use APIPA instead of > > conventional IP for network. How reliable is this APIPA? > > > > J. > > > > "Jack-MVP" wrote: > > > >> Hi > >> It might be that "Someone" meant to run the two with NetBEUI and > >> crossover > >> cable. > >> NetBEUI does not work with IPs but with computers names. > >> If the computers have any other Network/Internet connection, then you > >> need > >> TCP/IP anyway. > >> Configuring two computers with static IPs take few minutes. > >> In any case if you want to play with Win XP and NetBEUI. > >> http://www.ezlan.net/netbeui.html > >> Jack (MS, MVP-Networking) > >> > >> "Johnny" <Joh***@discussions.microsoft.com> wrote in message > >> news:581252BE-F1F1-4693-89B8-3BEC392842F7@microsoft.com... > >> > Lab environment: > >> > 2 computers > >> > No DHCP server > >> > No Router > >> > No Switch > >> > > >> > I know the faster way to make two computers to talk to each other is > >> > using > >> > a > >> > cross-over cable and assign static IP address on each one of them. > >> > > >> > Somone told me there is another way to do it, and I just want to > >> > confirm > >> > this with the experts here. He said two computers can talk to each > >> > other > >> > just > >> > by computer_name, without any IP address. > >> > > >> > My question: How reliable is this? > >> > > >> > PROS & CONS? > >> > > >> > All the comments are welcome. > >> > > >> > Thanks > >> > > >> > J. > >> > > >> > >> > > Then install NetBEUI ( it takes 3 minutes).
NetBEUI can leave in parallel to TCP/IP, so No other changes are needed. Jack (MS, MVP-Networking) Show quoteHide quote "Johnny" <Joh***@discussions.microsoft.com> wrote in message news:90052E38-5EF4-4056-BA71-B212B1DFF8B3@microsoft.com... > Needs: commmunicate by name between these 2 computers, via cross-over or > switch. > > "Jack-MVP" wrote: > >> Hi >> The world is full of mysteries, and this might be one of them. ;). >> I have No clue what, and why. If "SomeOne" can not explain clearly, and >> you >> do not have any unusual specific needs, then forget about it. >> Jack (MS, MVP-Networking) >> >> "Johnny" <Joh***@discussions.microsoft.com> wrote in message >> news:8E403762-190D-4F40-974D-6B71AEAB3760@microsoft.com... >> > hi Jack, >> > >> > I used to configure NetBEUI back in the old days for DOS >> > network/Win95/98/NT/XP. >> > But now we don't use NetBEUI any more, this person is saying to use >> > "Link-Local Address" I guess it's the same as APIPA to communicate >> > these >> > two >> > computers. >> > I just don't understand why he preferred to use APIPA instead of >> > conventional IP for network. How reliable is this APIPA? >> > >> > J. >> > >> > "Jack-MVP" wrote: >> > >> >> Hi >> >> It might be that "Someone" meant to run the two with NetBEUI and >> >> crossover >> >> cable. >> >> NetBEUI does not work with IPs but with computers names. >> >> If the computers have any other Network/Internet connection, then you >> >> need >> >> TCP/IP anyway. >> >> Configuring two computers with static IPs take few minutes. >> >> In any case if you want to play with Win XP and NetBEUI. >> >> http://www.ezlan.net/netbeui.html >> >> Jack (MS, MVP-Networking) >> >> >> >> "Johnny" <Joh***@discussions.microsoft.com> wrote in message >> >> news:581252BE-F1F1-4693-89B8-3BEC392842F7@microsoft.com... >> >> > Lab environment: >> >> > 2 computers >> >> > No DHCP server >> >> > No Router >> >> > No Switch >> >> > >> >> > I know the faster way to make two computers to talk to each other is >> >> > using >> >> > a >> >> > cross-over cable and assign static IP address on each one of them. >> >> > >> >> > Somone told me there is another way to do it, and I just want to >> >> > confirm >> >> > this with the experts here. He said two computers can talk to each >> >> > other >> >> > just >> >> > by computer_name, without any IP address. >> >> > >> >> > My question: How reliable is this? >> >> > >> >> > PROS & CONS? >> >> > >> >> > All the comments are welcome. >> >> > >> >> > Thanks >> >> > >> >> > J. >> >> > >> >> >> >> >> >> Johnny - first thanks to Jack - NetBEUI vice NetBIOS - "ad-hoc" pertains to
a wireless connection between two computers - wired are referred to as "peer-to-peer". 
Other interesting topics
Need help with an Internet access problem
Computers in same workgroup not recognizing each other Can't share files all of a sudden Networking failure again Neeed help 2 dsl connections on 1 pc Setting XP-Pro's Network Permissions "Network cable unplugged" How to change a .flv video file to view in WMP; New Network Setup |
|||||||||||||||||||||||
