From Newsgroup: alt.comp.os.windows-11

Hi All.

I just got off a remote session with a customer. They somehow
have a second router hooked up somewhere that is handing out
ipv6 addresses.

Other than going in to their facility in person and checking
behind EVERY desk at EVERY Ethernet outlet, is there a way to
disable the stinker?

None of their browsers will work with ipv6 addresses either.
An as soon as their ipv4 dhcp address expire ...

I find this at times when folk want extra Ethernet ports
and use a route instead of an simple hub only hub
(a layer 2 switching hub is still a hub).

-T
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On 29/01/2026 00:06, T wrote:

Hi All.

I just got off a remote session with a customer.  They somehow
have a second router hooked up somewhere that is handing out
ipv6 addresses.

Other than going in to their facility in person and checking
behind EVERY desk at EVERY Ethernet outlet, is there a way to
disable the stinker?

None of their browsers will work with ipv6 addresses either.
An as soon as their ipv4 dhcp address expire ...

I find this at times when folk want extra Ethernet ports
and use a route instead of an simple hub only hub
(a layer 2 switching hub is still a hub).

-T

It's all Donald Trump's fault! He's destroying everything. He broke
TikTok, too. I posted videos criticising Trump, and they were censored immediately. Videos criticising the 'Dear Leader' are not permitted on
the platform.








--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

T wrote:

Hi All.

I just got off a remote session with a customer.  They somehow
have a second router hooked up somewhere that is handing out
ipv6 addresses.

Other than going in to their facility in person and checking
behind EVERY desk at EVERY Ethernet outlet, is there a way to
disable the stinker?

No.

Go there and charge them accordingly.
--
Graham J
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On 1/29/26 12:18 AM, Graham J wrote:

T wrote:

Hi All.

I just got off a remote session with a customer.  They somehow
have a second router hooked up somewhere that is handing out
ipv6 addresses.

Other than going in to their facility in person and checking
behind EVERY desk at EVERY Ethernet outlet, is there a way to
disable the stinker?

No.

Go there and charge them accordingly.

Appt set for Friday afternoon.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

T wrote:
[snip]

Go there and charge them accordingly.

Appt set for Friday afternoon.

What did you find?
--
Graham J
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On 1/31/26 4:53 AM, Graham J wrote:

T wrote:
[snip]

Go there and charge them accordingly.

Appt set for Friday afternoon.

What did you find?

No extra router.

What a difference being on site makes!

The old printer that had not worked for over four years
got tossed in the trash. Finally!

The newer printer with the local IPv6 address totally
had its networking trashed.

IPv4 was no where to be found in network settings.
IPv6 was also missing. Could not find a network
or system reset.

I did

[1] a power cycle
[2] firmware upgrade
[3] Network reset (its showed up)

All the network setting finally show up. I configured
IPv4 for DHCP and turned IPv6 off.

And everyone now prints!

-T


--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

T wrote:
[snip]

What did you find?

No extra router.

What a difference being on site makes!

[snip]>

All the network setting finally show up.  I configured
IPv4 for DHCP and turned IPv6 off.

And everyone now prints!

Good work!
--
Graham J
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On Sun, 2/1/2026 5:50 AM, T wrote:

No extra router.

What a difference being on site makes!

The old printer that had not worked for over four years
got tossed in the trash. Finally!

The newer printer with the local IPv6 address totally
had its networking trashed.

IPv4 was no where to be found in network settings.
IPv6 was also missing.  Could not find a network
or system reset.

I did

[1] a power cycle
[2] firmware upgrade
[3] Network reset (its showed up)

All the network setting finally show up.  I configured
IPv4 for DHCP and turned IPv6 off.

And everyone now prints!

-T

That's what it says on the side of your business vehicle.

"King Of Printing"

Even people with no printer, have discovered that
now they can print!

Paul


--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

Even people with no printer, have discovered that
now they can print!

Yes, it's true that the origins of printing technology can be traced
back to China. The Chinese invented **woodblock printing** around the
9th century during the Tang Dynasty. This method involved carving an
entire page of text or images onto a wooden block, then inking it and
pressing it onto paper or cloth.

However, the Chinese also developed **movable type printing** much
earlier than Europe. The most famous early example is **Bi Sheng's
movable type** printing around the 1040s during the Song Dynasty.
Instead of carving an entire page on one block, movable type allowed for individual characters to be rearranged and reused, which made printing
much more efficient.

While Gutenberg's printing press, invented in the 15th century in
Germany, is often credited with revolutionising printing in Europe, the Chinese innovations in printing laid the groundwork for later
developments. In fact, it's believed that the **knowledge of Chinese printing** spread to the Middle East and Europe along trade routes like
the Silk Road.

So, in short, the invention of printing technology did originate in
China, though it evolved over time and spread across different cultures.


--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On Sun, 1 Feb 2026 02:50:03 -0800, T <T@invalid.invalid> wrote:

On 1/31/26 4:53 AM, Graham J wrote:

T wrote:
[snip]

Go there and charge them accordingly.

Appt set for Friday afternoon.

What did you find?

No extra router.

What a difference being on site makes!

The old printer that had not worked for over four years
got tossed in the trash. Finally!

The newer printer with the local IPv6 address totally
had its networking trashed.

IPv4 was no where to be found in network settings.
IPv6 was also missing. Could not find a network
or system reset.

I did

[1] a power cycle
[2] firmware upgrade
[3] Network reset (its showed up)

All the network setting finally show up. I configured
IPv4 for DHCP and turned IPv6 off.

And everyone now prints!

IMHO, shared network resources, such as printers, should never be
configured to use DHCP to acquire an address. Sooner or later, there's
going to be a problem there.

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On 2026-02-02 02:49, Char Jackson wrote:

On Sun, 1 Feb 2026 02:50:03 -0800, T <T@invalid.invalid> wrote:

I did

[1] a power cycle
[2] firmware upgrade
[3] Network reset (its showed up)

All the network setting finally show up. I configured
IPv4 for DHCP and turned IPv6 off.

And everyone now prints!

IMHO, shared network resources, such as printers, should never be
configured to use DHCP to acquire an address. Sooner or later, there's
going to be a problem there.

I had to set up a home printer to DHCP, using the home router to hand
out the address.

The printer has no display. It is configured using an app on a
smartphone. Kind of. The easiest way to give it a fixed address was
DHCP, after finding how to print a network report page and find the MAC.
--
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

Char Jackson wrote on 2/1/2026 6:49 PM:

On Sun, 1 Feb 2026 02:50:03 -0800, T <T@invalid.invalid> wrote:

On 1/31/26 4:53 AM, Graham J wrote:

T wrote:
[snip]

Go there and charge them accordingly.

Appt set for Friday afternoon.

What did you find?

No extra router.

What a difference being on site makes!

The old printer that had not worked for over four years
got tossed in the trash. Finally!

The newer printer with the local IPv6 address totally
had its networking trashed.

IPv4 was no where to be found in network settings.
IPv6 was also missing. Could not find a network
or system reset.

I did

[1] a power cycle
[2] firmware upgrade
[3] Network reset (its showed up)

All the network setting finally show up. I configured
IPv4 for DHCP and turned IPv6 off.

And everyone now prints!

IMHO, shared network resources, such as printers, should never be
configured to use DHCP to acquire an address. Sooner or later, there's
going to be a problem there.

My router(s) are configured to use DHCP and set with a small range of
starting and ending ip addresses. The printer(s)[two printers, each in a different geographic location, one on each router] are assigned a fixed,
DHCP dispensed ip address.
- Mac Filtering(Access control) is also enabled(for those printers and
all other devices) with an 'Allow' control, but new devices are not
allowed until configured(assign ip with its MAC, allow in Access
Control/Mac filter).
- Guest network is almost always disabled unless necessary for visitors.

The printers are shared on the home network, across my three devices,
each device with 3 different but exact same Windows logons(two MSA[mine, spouse]; one Local admin). Other devices(children, grandchildren laptops, phones, iPads with assigned ip address and access control allowed MACs
all have use of the printers in each geographic location).

Never had an issue/problem with any of the printers - one is wifi
connected, the other a lan connection).


The only issue that I've come across are iPhones which rotate MAC
addresses via their default enabled Private Wi-Fi address. Fortunately,
for those, it can be disabled specifically, and only for their wifi
connection to my two router/networks and not impacting the use of
Private-wifi on their other networks(Home, work[some with extra security control for intellectual property protection]).
--
...w¡ñ§±¤ñ
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On Mon, 2 Feb 2026 09:59:58 -0700, ...w¡ñ§±¤ñ <winstonmvp@gmail.com>
wrote:

Char Jackson wrote on 2/1/2026 6:49 PM:

IMHO, shared network resources, such as printers, should never be
configured to use DHCP to acquire an address. Sooner or later, there's
going to be a problem there.

My router(s) are configured to use DHCP and set with a small range of >starting and ending ip addresses. The printer(s)[two printers, each in a >different geographic location, one on each router] are assigned a fixed, >DHCP dispensed ip address.

My objection to that approach stems from multiple experiences where
someone messes with the DHCP server, not remembering that there are
resources on the network that are intended to be at a static address.

<snip>

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On 2026-02-03 02:45, Char Jackson wrote:

On Mon, 2 Feb 2026 09:59:58 -0700, ...w¡ñ§±¤ñ <winstonmvp@gmail.com> wrote:

Char Jackson wrote on 2/1/2026 6:49 PM:

IMHO, shared network resources, such as printers, should never be
configured to use DHCP to acquire an address. Sooner or later, there's
going to be a problem there.

My router(s) are configured to use DHCP and set with a small range of
starting and ending ip addresses. The printer(s)[two printers, each in a
different geographic location, one on each router] are assigned a fixed,
DHCP dispensed ip address.

My objection to that approach stems from multiple experiences where
someone messes with the DHCP server, not remembering that there are
resources on the network that are intended to be at a static address.

<snip>

RTFM
--
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On Mon, 2 Feb 2026 13:19:02 +0100, "Carlos E.R."
<robin_listas@es.invalid> wrote:

On 2026-02-02 02:49, Char Jackson wrote:

IMHO, shared network resources, such as printers, should never be
configured to use DHCP to acquire an address. Sooner or later, there's
going to be a problem there.

I had to set up a home printer to DHCP, using the home router to hand
out the address.

The printer has no display. It is configured using an app on a
smartphone. Kind of. The easiest way to give it a fixed address was
DHCP, after finding how to print a network report page and find the MAC.

Sometimes you have to, but it doesn't sound ideal.

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On Tue, 3 Feb 2026 03:15:38 +0100, "Carlos E.R."
<robin_listas@es.invalid> wrote:

On 2026-02-03 02:45, Char Jackson wrote:

On Mon, 2 Feb 2026 09:59:58 -0700, ...w¡ñ§±¤ñ <winstonmvp@gmail.com>
wrote:

Char Jackson wrote on 2/1/2026 6:49 PM:

IMHO, shared network resources, such as printers, should never be
configured to use DHCP to acquire an address. Sooner or later, there's >>>> going to be a problem there.

My router(s) are configured to use DHCP and set with a small range of
starting and ending ip addresses. The printer(s)[two printers, each in a >>> different geographic location, one on each router] are assigned a fixed, >>> DHCP dispensed ip address.

My objection to that approach stems from multiple experiences where
someone messes with the DHCP server, not remembering that there are
resources on the network that are intended to be at a static address.

<snip>

RTFM

Good one. :)

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On 2026-02-03 03:22, Char Jackson wrote:

On Tue, 3 Feb 2026 03:15:38 +0100, "Carlos E.R." <robin_listas@es.invalid> wrote:

On 2026-02-03 02:45, Char Jackson wrote:

On Mon, 2 Feb 2026 09:59:58 -0700, ...w¡ñ§±¤ñ <winstonmvp@gmail.com> >>> wrote:

Char Jackson wrote on 2/1/2026 6:49 PM:

IMHO, shared network resources, such as printers, should never be
configured to use DHCP to acquire an address. Sooner or later, there's >>>>> going to be a problem there.

My router(s) are configured to use DHCP and set with a small range of
starting and ending ip addresses. The printer(s)[two printers, each in a >>>> different geographic location, one on each router] are assigned a fixed, >>>> DHCP dispensed ip address.

My objection to that approach stems from multiple experiences where
someone messes with the DHCP server, not remembering that there are
resources on the network that are intended to be at a static address.

<snip>

RTFM

Good one. :)

Thanks :-). Of course, we should also WTFM.

Documenting the configuration of a router is an horrible task. Recently (months), my ISP handed me a new router. I had to print to PDF all the configuration pages of the router (14 files for the "simple" config, and
66 for the advanced setup), one by one. Then do the new router, which thankfully has a similar structure, and redo everything page by page.
--
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;
--- Synchronet 3.21a-Linux NewsLink 1.2