Re: Finidng the IP Address of MY Networked Printer
From: Chuck (none_at_example.net)
Date: 09/13/04
- Next message: Chuck: "Re: bridge.dll"
- Previous message: Eric Cross [MVP]: "Re: Two Lan Connections with 1 NIC"
- In reply to: Dale: "Finidng the IP Address of MY Networked Printer"
- Messages sorted by: [ date ] [ thread ]
Date: 13 Sep 2004 13:35:14 -0500
On Mon, 13 Sep 2004 10:13:33 -0700, Dale <dbh@ix.netcom.com> wrote:
>I have sucessfully installed a home network where my Win2K computer
>(which is connected by a cable to a wireless router) can communicate
>with a Win98 computer (connected by a wireless card) by using the same
>Workgroup Name. I am using the Win98 machine as a print server to
>drive a large printer that cannot fit in the same room as the Win2K
>computer. I have just purchased a program called ImagePrint that
>allows the use of either local or networked printers, but it requires
>the IP address of the networked device. How do I find the IP address
>of the networked printer? Does my type of network even assign IP
>addresses to periperal devices (as I recall, I now address the printer
>as: \\machinename\printername)? Would I be better off buying a
>dedicated wireless print servicer (such as the ones that Belkin,
>Netgear, or others sell)? Sorry for all of the questions, but I
>cannot seem to work this out by myself. TIA.
>
>Dale
Dale,
Is the printer directly attached to the Win98 computer (print server)? If so,
then the ip address of the printer will be the ip address of the Win98 computer.
You will then address the printer as \\Win98IPAddress\printername.
If ImagePrint allows you to identify the printer as
\\Win98IPAddress\printername, then you're OK. If ImagePrint requires a straight
IP address, such as PrinterIPAddress, then you will indeed need to purchase a
print server to allow you to connect the printer directly to the network.
When connecting a printer to a wireless LAN, you will get the best performance
if you can use a wired printer server. A two way wireless connection (computer
to router, and printer to router), does not work well for print jobs.
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
- Next message: Chuck: "Re: bridge.dll"
- Previous message: Eric Cross [MVP]: "Re: Two Lan Connections with 1 NIC"
- In reply to: Dale: "Finidng the IP Address of MY Networked Printer"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|