View Single Post
  #9  
Old October 23rd 19, 10:59 PM posted to alt.windows7.general,microsoft.public.windowsxp.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Printer Present For Real

Boris wrote:
Boris wrote in
.198:

Paul wrote in :

Boris wrote:
"NY" wrote in :

"Jeff Barnett" wrote in message
...
Set your router to give the same IP address every time to the

printer.
That enables you to create a shortcut in your bookmarks for that
printer.
Essentially this allows you to recall the printer's name rather than
its
IP address. You'll appreciate that convenience as you age.
Most network printers that I have set up require a static/reserved IP
address. My Epson SX515W configured itself on Printer Properties |

Ports
to
use "Standard TCP/IP Port" with the IP address that the printer was
allocated when it was detected. When I rebooted my router and the
printer
was given a different IP address by DHCP, communication stopped. I

had
a
choice of configuring the printer to use a static IP address or
configuring
my router's DHCP to reserve the same IP address for the printer; I

chose
the
latter because devices with static IPs are a clash waiting to happen!

I
do
the same for my security cameras so I can browse to them by IP from

my
phone
and can configure port-forwarding to access them from outside my LAN.


Hmmm...got me to thinking.

Yesterday I swapped out wireless routers. The old Dlink 524, after

many
years of faithful use, wouldn't hold the WAN connection anymore. I

pulled
out a brand new Linksys/Cisco WRT54G router. (I have two of them from
when other first adopters didn't even bother to open the boxes, and

moved
on to something newer.) I now at least have better security.

The Dl 524 was also used to connect over the home network to print
wirelessly to a Brother HL-2270DW mono laser printer. This printer is
capable of printing wirelessly, or via USB or ethernet. It was set up
wirelessly when first purchased in 2011 so I could print from laptops
around the house.

I printed out the network configuration from the Brother printer, and

it
showed "IP 192.168.0.98, (set manually)".

I set up the 'new' WRT54G, which handed out IP 192.168.1.106 via DHCP,

but
the printer didn't recognize it. Wired devices did, however. I

followed
Brother's instructions on how to change the IP, but couldn't even get

into
the browser based settings. I had to completely uninstall all Brother
drivers and software, and reinstall, to get the printer to find and
connect to the WRT54G.

Now, when I print out the Brother network configuration, it shows "IP
192.168.1.106 (via DHCP)".

Your comment that everytime you had to reset your router caused a
disconnect with the statically set printer IP, got me thinking, that

ever
since I originally set up this Brother printer, I had reset (power

down,
power back up) the Dl 524, and the printer had always shown that it's

IP
was 'set manually, yet the printer never lost connection.

I wonder why.
There are other ways a printer can "broadcast" its presence.

https://support.brother.com/g/b/faqe...rintable.aspx?

c=us&lang=en&prod=nc7100w_all&faqid=faq00000232_00 0&printable=true
Paul

I did notice that that article said SSDP was disabled by default. The

HL-
2270DW reports itseld as Model NC-7800W.

I looked at all of the printer settings and found no SSDP setting to
toggle on or off.

At any rate, I looked at my records, and when first installed on

2/14/12,
the IP was 192.168.0.98 set manually. Yesterday, the IP was still
192.168.0.98 set manually. Are you saying that if the printer is SSDP
capable, the printer would 'tell' the router what IP it insisted on

using?
Thanks.


By the way, the printer is set up in infrastructure mode. The router is
connected to a Windows 7 machine via ethernet. There are other desktops,
one Windows 10, one XP, connected the LAN ports.

Four Windows 10 laptops connect to the router (wirelessly).

All pcs can print to the printer.


When there are alternative protocols on a LAN, they allow other
ways of discovering devices.

For example, if I'm a printer, and I am given an IP via DHCP,
I can announce in a loud voice "I'm a printer and I'm at 192.168.0.98".

A "name" server is a server task running somewhere, that records
these announcements. Maybe a freshly booted computer yells out
"Who's out there", and the nameserver can say "I heard a printer
over on 192.168.0.98 and his name is Fred". so rather than
all discovery mechanisms working in one direction, there are
alternatives.

I think if one of those name serving things is working,
you get a nice looking icon in the devices section.

Half way down this page, is a screenshot from Windows 7,
showing detected devices. There's even an Apple iPhone
in one of those shots - how did that get there ??? :-)

https://www.sevenforums.com/tutorial...m-icons-3.html

I don't think WinXP does it with quite that much style.

Paul


Ads