Solved Help connecting a network printer to a switch

August 28, 2012 at 10:30:36
Specs: Windows 7 SP1
I have absolutely zero knowledge of networking. I've had a friend who's finishing his degree in network engineering come over to help me connect a printer to a d-link switch, so it can be accessed in a LAN (no internet connection).
We've managed to ping the printer port succefully, but couldn't send print jobs to it.
The person who sold me the printer told me yesterday the problem could be not using the same IP range for the router and printer.
I've been fiddling with it ever since....

The printer has IP 192.168.1.250, Gateway 192.168.1.254, Subnet 255.255.255.0
I arbitrarily changed default router IP 192.168.0.1, to 192.168.1.248 (Subnet 255.255.255.0).

In the WAN settings i'm trying to configure my computer's Static IP to the same range using IP 192.168.1.249 (Gateway 192.168.1.254).
Using the same Subnet as the router for the WAN will cause conflict between WAN and LAN.
What IP should i use? And should i change anything else?

Thanks in advance.


See More: Help connecting a network printer to a switch

Report •


✔ Best Answer
August 28, 2012 at 16:31:04
Finally figured it out.
After a long and tedious trial-and-error odyssey, resetting the router, changing IPs back and forth on both the printer and router.
It was obvious the problem wasn't in the network itself.
Turns out there's a configuration in the printer to allow an IP to issue commands via the network. Configuring this "Access Control" feature to my machine IP solved the issue.
Pretty basic thing in retrospect, but no one ever thought of trying it...
Sorry to bother Curt and Dan. And thanks for your quick replies.


#1
August 28, 2012 at 11:12:15
What make/model printer?

What OS are you running?

How are you assigning IP's? Static or DHCP?

If you can ping the printer then you've established connectivity. Have you configured your computer to print to a network port and installed the correct drivers?


Report •

#2
August 28, 2012 at 12:09:44
192.168.1.0/24 (ie: subnet mask 255.255.255.0) will have a range of IP's as follows:

192.168.1.1 through to 192.168.1.254

So all the IP's you've chosen are valid and should be able to communicate with each other. Although why you went through the trouble of changing it, I don't know.

Most typica SOHO Routers create a DHCP Scope similar to the following (using your subnet)

192.168.1.100 through to 192.168.1.199

I will say this thought, it's usual, and preferable, to have your gateway IP be .1 This will make your life simpler should you ever have to supernet.

Having said that, if you've configured your scope as above, the IP's you've chosen to use are outside of it so you needn't worry about making reservations or having duplicate IP errors.

You said, "We've managed to ping the printer port succefully, but couldn't send print jobs to it."

This tells me the netowrk is configured correctly and working. The issue seems to be the printer you're trying to create on the client. I suggest you try redoing the printer on the client. First, delete the one you've already created and then do the following:

Click on my name above in this response and read my “how-to” guide titled, “Installing a Network Printer: version 2

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#3
August 28, 2012 at 15:30:52
The printer is a Ricoh Aficio AP3800C. Latest drivers (2.31) for Windows 7 x64 installed from this address.
The drivers are a little fishy. There's no installer, only a decompressor. And i have to install manually through windows.
Installed as network printer with IP 192.168.1.250.
All TCP/IP, Telnet and other windows network components are present.
I've got DHCP deactivated on both the router and the printer. But i've tried it with DHCP on.
I've already tried deleting and reinstalling printer drivers. I've done it on two separate computers (both win7).
The printer is detected on the network, but print jobs don't go through.

I don't understand enough about printers and networks to troubleshoot this.

Unanswered question: what subnet address should i use for WAN and LAN? Using the same IP results in conflict.


Report •

Related Solutions

#4
August 28, 2012 at 16:31:04
✔ Best Answer
Finally figured it out.
After a long and tedious trial-and-error odyssey, resetting the router, changing IPs back and forth on both the printer and router.
It was obvious the problem wasn't in the network itself.
Turns out there's a configuration in the printer to allow an IP to issue commands via the network. Configuring this "Access Control" feature to my machine IP solved the issue.
Pretty basic thing in retrospect, but no one ever thought of trying it...
Sorry to bother Curt and Dan. And thanks for your quick replies.

Report •

#5
August 29, 2012 at 07:00:23
No worries, you didn't bother us. In fact, by coming back in here and writing what did resolve it, and including the make/model, chances are you'll help someone else in the future.

So thank you for coming back and putting that in here!

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •


Ask Question