Groups | Search | Server Info | Login | Register
Groups > comp.os.ms-windows.networking.misc > #81
| From | VanguardLH <V@nguard.LH> |
|---|---|
| Newsgroups | microsoft.public.windowsxp.general, alt.comp.os.windows-xp, comp.os.ms-windows.networking.misc |
| Subject | Re: LAN Connections in XP |
| Date | 2017-05-12 15:14 -0500 |
| Organization | Usenet Elder |
| Message-ID | <enmjcpFg2ooU1@mid.individual.net> (permalink) |
| References | <ilrahc96e8tk4n9nehb6d4j7j9l12f80uk@4ax.com> <591578f6$0$790$e4fe514c@news.xs4all.nl> <pvtbhcda66jlule6aoogmv380hladp3n7b@4ax.com> |
Cross-posted to 3 groups.
Steve Hayes <hayesstw@telkomsa.net> wrote: > But both connect to the router on the same LAN -- my XP computer using > Ethernet, and my wife's using WiFi. Some routers let you isolate different network segments (by using different network segments on each port/wifi to the router). That is, they assign a different network segment to each port/wifi connect, allow outbound connects from each port/wifi connect to the Internet, but do not allow traffic between the port/wifi connects. Are all your hosts on the same network segment? Are that all assigned something like xxx.xxx.xxx.NNN where the xxx.xxx.xxx portion is the same for all of them? Is the submask for each the same? As per Wiesers suggestion, you can use ipconfig /all to see the IP address hence network segment and submask assigned to the NIC(s) in each of your hosts. You also need to make sure that each of your hosts and your router are supporting the same type of IP addressing. There is IPv4 and IPv6. While I had hosts that supported both, I had an old router that only supported IPv4. When I got a newer router that supported IPv6, it was assigning both IPv4 and IPv6 addresses to my hosts. IPv6 is pre-enabled on Windows Vista+; however, IPv6 is not pre-enabled on Windows XP. See: https://www.ghacks.net/2011/02/06/how-to-enable-ipv6-on-windows-xp/ With a router that supports both, your hosts should have both types of IP addresses assigned but you need to make sure they are within the same network segment and that your router is not isolating traffic between its ports/wifi connections.
Back to comp.os.ms-windows.networking.misc | Previous | Next — Previous in thread | Next in thread | Find similar
LAN Connections in XP Steve Hayes <hayesstw@telkomsa.net> - 2017-05-12 10:14 +0200
Re: LAN Connections in XP "R.Wieser" <address@not.available> - 2017-05-12 10:57 +0200
Re: LAN Connections in XP Steve Hayes <hayesstw@telkomsa.net> - 2017-05-12 20:01 +0200
Re: LAN Connections in XP "R.Wieser" <address@not.available> - 2017-05-12 21:38 +0200
Re: LAN Connections in XP Steve Hayes <hayesstw@telkomsa.net> - 2017-05-13 01:54 +0200
Re: LAN Connections in XP Char Jackson <none@none.invalid> - 2017-05-13 12:01 -0500
Re: LAN Connections in XP Steve Hayes <hayesstw@telkomsa.net> - 2017-05-13 20:29 +0200
Re: LAN Connections in XP Steve Hayes <hayesstw@telkomsa.net> - 2017-05-13 20:31 +0200
Re: LAN Connections in XP Char Jackson <none@none.invalid> - 2017-05-14 10:32 -0500
Re: LAN Connections in XP Steve Hayes <hayesstw@telkomsa.net> - 2017-05-15 05:54 +0200
Re: LAN Connections in XP VanguardLH <V@nguard.LH> - 2017-05-15 03:11 -0500
Re: LAN Connections in XP Shadow <Sh@dow.br> - 2017-05-15 11:28 -0300
Re: LAN Connections in XP Steve Hayes <hayesstw@telkomsa.net> - 2017-05-16 06:34 +0200
Re: LAN Connections in XP Lucifer Morningstar <not@for.resale> - 2017-05-16 14:48 +1000
Re: LAN Connections in XP Shadow <Sh@dow.br> - 2017-05-16 09:29 -0300
Re: LAN Connections in XP Steve Hayes <hayesstw@telkomsa.net> - 2017-05-17 05:51 +0200
Re: LAN Connections in XP VanguardLH <V@nguard.LH> - 2017-05-12 15:14 -0500
Re: LAN Connections in XP Lucifer Morningstar <not@for.resale> - 2017-05-14 09:37 +1000
Re: LAN Connections in XP Shadow <Sh@dow.br> - 2017-05-14 06:47 -0300
Re: LAN Connections in XP Char Jackson <none@none.invalid> - 2017-05-14 10:35 -0500
Re: LAN Connections in XP Shadow <Sh@dow.br> - 2017-05-14 13:27 -0300
csiph-web