Groups | Search | Server Info | Login | Register

Groups > comp.os.ms-windows.networking.misc > #92

Re: LAN Connections in XP

Cross-posted to 3 groups.

Show key headers only | View raw

Host #1:
IPv4 Address. . . . . . . . . . . : 192.168.11.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.11.1
DHCP Server . . . . . . . . . . . : 192.168.11.1

Host #2:
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1

Host #3:
IPv4 Address. . . . . . . . . . . : 192.168.0.8(Preferred) 
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1

Host #2 just says "IP address", not "IPv4 address".  Is host #2 your
Windows XP host?

Does your router actually have 2 DHCP servers to serve different
subnets?  I don't remember seeing consumer-grade routers with multiple
DHCP servers.  If it has just one DHCP server (likely), what is its IP
address and [sub]netmask values?

Are you chaining routers (one router chains to the main router that goes
to the cable modem)?  Are you using an AP (access point) for wi-fi
access that chains to the main router going to the cable modem?  If so,
did you leave the DHCP server enabled in the downstream router or AP
instead of having it pass that traffic up to the main router's DHCP
server?  If you don't want subnetting then use the downstream router or
AP as a simple switch, not as a router and not using its DHCP server.

Host #1 = 192.168.11.10
Host #2 = 192.168. 0. 2
Host #3 = 192.168. 0. 8
(spaces added only to provide alignment for readability)

You've got 2 hosts on 192.168.0.x and one on 192.168.11.x.  Two are have
a 3rd octet of 0 (zero) while one has a 3rd octet of 11.  While all of
them use 255.255.255.0 for the subnet mask, that mask only covers
addresses in the 192.168.1.0/24 range (or 192.168.1.0 to 192.168.1.255).
192.168.11.x is outside that range so it is in a different subnet than
for your other two hosts.  If you don't want to change the assigned IP
address to each host, you need to change their subnet mask so they are
within the same subnet, like 255.255.0.0 (or 255.255.240.0 at a
minimum).

http://jodies.de/ipcalc?host=192.168.11.10&mask1=20&mask2=

To get 11.x into the same subnet as for 0.x, you need the netmask to
have zeros (which bits to ignore or put under the same subnet) under the
maximum significant binary digits for an address.  11 decimal = 1101
binary.  That's 4 more digits you want to include in addressing to stay
in the same subnet.

https://en.wikipedia.org/wiki/Subnetwork
  Traffic is exchanged (routed) between subnetworks with special 
  gateways (routers) when the routing prefixes of the source address and 
  the destination address differ. A router constitutes the logical or 
  physical boundary between the subnets.
  
That is true *if* the router is configured to allow traffic between its
subnets.  Is it?  

If you want 11.x and 0.x to be in the same subnet, does your router use
a subnet mask of 255.255.240.0, or lower?  If you want one host's IP
address to be in a subnet of another host, their subnet masks must span
a range to include both addresses.  The subnet mask defines the
boundaries (addressing range) of an IP subnet.  The router might have a
feature to allow traffic between subnets (if enabled).  It might not.
Tough to know what is in your network, how devices are chained, and how
they are configured.  Subnetting might be the problem.  Might not if the
router(s) were configured to pass traffic between them.

For example, the corporate network did not want our high volume of test
traffic to our test hosts on their network.  We employed a switch that
simply isolated each subnet.  Traffic on the alpha lab's subnet stayed
in the alpha lab's network and did not impinge on the corporate network;
however, select alpha lab hosts in the switch's config were allowed to
connect to the corporate subnet.  Routers have switches, too.  Traffic
isolation was afforded by restricting traffic across subnets.

Are you sure the printer is configured as a shareable resource on your
Windows XP host?  On the host (Windows XP) to which the printer is
attached, go to Control Panel -> Printers and Other Hardware -> Printers
and Faxes.  Right-click on the printer.  Under the Sharing tab, is the
printer shared?  Under the Additional Drivers button, you have to enable
the driver(s) that each of your other host(s) will use.  Also, back
under the Security tab (of the Windows XP host to which the printer is
connected), check the Everyone security group is listed as having Print
permission.  Being able to find a printer doesn't necessarily grant
permission to use it.  "bought a new Brother printer and connected it to
my XP machine" does not say you installed the device's driver.

https://technet.microsoft.com/en-us/library/bb457001.aspx
https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/print_security_permissionsw.mspx?mfr=true

When you get prompted that you need permissions for Administrator, it is
NOT asking for you to use an admin-level account on the host you are
using.  It is asking for the admin on the OTHER host to grant your
permission to connect there.  You have to go to other host to which you
are trying to connect (and to which the printer is connected) to grant
the host you are currently using to connect that other host.  

For whatever account name under which you log under on one host, did you
define an account on Windows XP by the same name and password?

Back to comp.os.ms-windows.networking.misc | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

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