Can't access network printer

September 18, 2009 at 02:22:24
Specs: Windows XP, Athlon X2 6000+/2GB
Hi.
Yesterday I created a small network consisting of 4 PC's and a network copier/printer. They are connected to Billion Wireles-G router (can't remember the exact model. It's at my friend's place). As for the PC's everything is fine but I haven't had luck accessing network printer. The printer in question is Xerox DocuColor 12. I set up the IP/subnet/gateway statically but no matter what I can't access it. Not even ping it. When I take the cable from the router and connect it directly to the PC it can be accessed. I'm out of ideas and I scouted the net in search for solution but didn't found one.

See More: Cant access network printer

Report •


#1
September 18, 2009 at 07:21:22
You need to print out the configuration page on the printer to verify it has the correct TCP/IP settings. I suspect it doesn't if you can't even ping it.

When you say, "When I take the cable from the router and connect it directly to the PC it can be accessed" what cable exactly are you talking about............a network cable or a printer cable?


Report •

#2
September 18, 2009 at 07:47:52
"When I take the cable from the router and connect it directly to the PC it can be accessed."

This should not be possible. Is this a Ethernet Cable or USB or what? If it is an ethernet cable then double check to make sure it is not a cross over cable.

Also, you said the printer is setup with a static IP so did you go into the Routers DHCP and make sure the Dynamic IP Range was set above that of the Printers IP or are you using static IPs for your Computers too?


Report •

#3
September 18, 2009 at 08:02:08
It is a Crossover Ethernet Cable. The router is capable of detecting what type of cable is used so I'm not sure that can cause a problem. I'll try using strait-trough cable later on. Until then any other ideas?

Edit: I tried using strait-trough cable but it didn't help.


Report •

Related Solutions

#4
September 18, 2009 at 10:51:07
A straight through won't work as you basically going from NIC to NIC and when connecting like devices, you need a crossover.

Yes, most modern switches do auto MDIX so you can use a straight through on them, but it's still my preference to always use a crossover in cases like this (one less thing to have to truobleshoot).

Anyhow, did you print out the printer's config and compare it to the config on your PC's?

If not, do so. The only thing that should differ is the actual IPaddress. Other than that, everything should be identical.


Report •

#5
September 18, 2009 at 11:06:12
I just printed out config and all seems just fine. I even enabled SMB so printer can bee seen as a computer in Workgroup but it also didn't help. It all works just fine when I connect the printer directly to the PC, using crossover cable.

Report •

#6
September 18, 2009 at 11:08:18
Also, you said the printer is setup with a static IP so did you go into the Routers DHCP and make sure the Dynamic IP Range was set above that of the Printers IP or are you using static IPs for your Computers too?

Report •

#7
September 18, 2009 at 11:18:12
I turned off DHCP in router. When it was on the router kept reseting it self, but thats a whole other story. I also tried pinging printer address directly from router but no reply there either.

Report •

#8
September 18, 2009 at 12:50:40
How did you setup the printer on the workstations? As a ip printer [new tcp/ip port]?
When connected network wise lights on the print server on?

Report •

#9
September 18, 2009 at 13:02:04
I can't even ping the printer's ip or access it's web interface so I didn't bother adding printer to any workstation. All lights that should be on are on.

Report •

#10
September 18, 2009 at 13:43:30
I can't even ping the printer's ip

This is why I said to print out the config.

Humor me, post the printer's config and also, open a command prompt window on one of your PC's and run the following command:

ipconfig /all

and put the output of that in the same post as the printer info.

Just the TCP/IP settings.


Report •

#11
September 18, 2009 at 14:02:41
Eh?

You write:
It all works just fine when I connect the printer directly to the PC, using crossover cable.
and
so I didn't bother adding printer to any workstation

Perhaps you need to clarify what "it all works" means to you.


Report •

#12
September 19, 2009 at 05:23:01
Curt R heres what you requested:

ipconfig /all

Windows IP Configuration
Host Name . . . . . . . . . . . . : racunar
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce 10/100 Mbps Ethernet
Physical Address. . . . . . . . . : **-**-**-**-**-**
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.12
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 208.67.222.222
208.67.220.220

Printer configuration:
TCP/IP
Protocol: Enabled
Interface: Ethernet
IP Address: 192.168.1.50
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.254
Broadcast Address: 192.168.1.255
Adress Resolution: Static
Host Name: DCCS50

LPD/LPR
Protocol: Enabled:
Max # of Connections: 16

SMB
NetBIOS/NetBEUI: Enabled
NetBIOS/IP: Enabled
Interface: Ethernet
SMB Name: XRX0001AF026DBC
Workgroup/Domain: WORKGROUP
Max # of Connections: 10
Connection Timeout: 10

Port Setup:
Ethernet
Interface: Enabled
MAC: **-**-**-**-**-**
Port Timeout: 300 seconds
Speed: 100 Mbps


wanderer:
When I (using the crossover cable) connect printer directly to PC I can access it (print, change setup, etc). But when i connect printer (and PC it was connected to) to router (without changing anything) that PC (and all others) can't even ping the printer but can comunicate with each other perfectly.


Report •

#13
September 19, 2009 at 05:34:45
Thanks for the printout.

Everything looks good and it should work. As for it not replying to pings, it could be set to not reply. The fact that you can print to it when it's connected directly to a PC via a crossover also tells me it should work.

I suggest you try setting up a printer on a client computer and see if you can't. See my "setup a printer" guide in the "Howtos" section of this website for proper procedure for connecting a network printer.


Report •

#14
September 19, 2009 at 05:50:48
That's the point. Everything is setup just as it should work, but it doesn't. Printer is not set not to answer to ping (I can ping it when he's connected directly). I tried printing from a PC he was connected to (when connected to router) but it didn't work. I even asked local copier repair service what could be the problem and they also didn't have a clue. I added another NIC to a PC and I'm going to share printer to other PC's but that means host PC must be turned on and that is what I was tryin to avoid in the first place.
Thank you for trying to help.

Report •

#15
September 21, 2009 at 10:40:46
"Adress Resolution: Static"

Looks like you are using a Static IP on your printer which is fine as long as you have setup a reservation in your Router for that IP. Have you done so or have you setup your IP Range to only go from 1-49?

Either way will work or you could just turn DHCP off on your router and use all static IPs for your computers.


Report •

#16
September 21, 2009 at 11:15:24
Printer should not have gateway or dns entries. Not required and can result in the equipment being hacked.

metalinspired if you can ping it when directly connected and you can print to it using ip port printing... then I can find nothing wrong with the printer or workstation setups.

Has to be a setting in the router causing the issue. This router also contain a firewall? I would go thru and check the settings to see what maybe blocked.

Doesn't lpr printing use port 9100? Perhaps its blocked on the router [though this is all on the lan side and routing/firewall should not be affecting this]?


Report •

#17
September 22, 2009 at 02:34:31
ace_omega:
DHCP is turned off in router and all PC's have static IP's.

wanderer:
While searching the web I found someone mention the same thing about gateway entries (maybe it was you). I tied that too. Went with 0.0.0.0 (since it won't let me set it to blank) and 127.0.0.1 but none produced any effect.
Yes. LPR printing does use port 9100 but even if it was blocked I should be able to ping the device (like I can ping other PC's in the network) since it uses different port. I also tried turning off firewall on the router but didn't help. If I get the time later during the day I'll write to Xerox and ask them if they know what's wrong.


Report •

#18
September 22, 2009 at 09:05:30
The effect is to cut internet access to the printer controls. A hospital had a bunch of monitoring equipment that also contained hard drives. These were hacked and the hard drives used to store illegal information.

This is what you are preventing with no gateway entry in the printer.

Not being able to ping thru the router would indicate to me the firewall is blocking icmp traffic globally.

I don't see any mention of a ping pc to pc test. Does ping work in this case? If not then that would confirm the issue with the router.


Report •

#19
September 23, 2009 at 01:13:37
PC to PC pinging works. I mentioned that I turned off firewall in router and even with that config it wouldn't work. Even the firmware update of a router didn't change anything. I'm thinking that something is not being routed but since in local network router acts as a switch that shouldn't be the case.

Report •

#20
September 25, 2009 at 08:17:24
Is it only one printer?

It could be simply that the NIC in your printer has failed. They do go out from time to time which why I keep spare Printer NICs along with Computer NICs.


Report •

#21
September 25, 2009 at 14:43:13
No, NIC is not dead. I can connect directly using a crossover cable...

Edit: It is only network printer there.


Report •


Ask Question