• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

using the route command

pontifex

Lifer
I know you can use the route command to allow 2 networks on different ip addresses to "see" each other.

we got a new printer/copier/scanner system in today that will allow you to scan to email but it won't send the email.
below is an example of how our network is set up:

the printer is on the 192.168.100.0 network
the email server is on the 192.168.200.0 network

the printer is set up with the correct ip addresses for everything.

I can't ping the printer from the email server but I can ping other computers on the 192.168.100.0 network because there is a route set to that network. Now one thing I'm not clear on is if both devices have to have the routes set. I'm thinking they do, though.

The printer has no way to create a route entry and there isn't a way to ping anything from the printer.

Is there any way I can get this to work? Let me know if you need more info and I can try to provide it.
 
Originally posted by: pontifex
I can't ping the printer from the email server but I can ping other computers on the 192.168.100.0 network because there is a route set to that network.

are you using a 24bit subnet mask? if theres a route to the 100net, the printer should respond. double check the subnet mask and default-gateway settings.

hosts dont need to know where to route packets to. if its outside its current network, then it consults the default-gateway (aka a router).

elaborate on your network hardware.
 
Originally posted by: jlazzaro
Originally posted by: pontifex
I can't ping the printer from the email server but I can ping other computers on the 192.168.100.0 network because there is a route set to that network.

are you using a 24bit subnet mask? if theres a route to the 100net, the printer should respond. double check the subnet mask and default-gateway settings.

computers dont need to know where to route packets to...thats a function of the default-gateway.

elaborate on your network hardware.

subnet mask is 255.255.255.0

elborate on network hardware? what exactly do you need to know?
 
what make / model devices are you using for your switches and routers.

if your able to ping from 192.168.200.0 to 192.168.100.0, your routes are fine.

if you are able to ping from a 192.168.100.0 computer to the printer, most likely your default gateway on the printer is wrong.
 
Originally posted by: jlazzaro
what make / model devices are you using for your switches and routers.

if your able to ping from 192.168.200.0 to 192.168.100.0, your routes are fine. check and recheck your printer settings.

i've checked printer settings multiple times. they are correct. there is 1 setting that shows in the config printout that i can't see in the actual screens. its enable gateway automatically. it is set to no but there is a gateway address listed and it is correct.

cisco and d-link switches. not sure what models.
 
are able to ping from a 192.168.100.0 computer to the printer?

internal or EIO network card for the printer? do you have link lights on the printers nic? have you swapped it out to eliminate a hardware issue? have you tried another switchport? if you were a hotdog would you eat yourself?
 
Originally posted by: jlazzaro
are able to ping from a 192.168.100.0 computer to the printer?

internal or EIO network card for the printer? do you have link lights on the printers nic? have you swapped it out to eliminate a hardware issue? have you tried another switchport? if you were a hotdog would you eat yourself?

well, it was a wrong address. apparently my boss changed the gateway for the 100 segment to another address for some reason and never bothered to tell me. :|
 
Back
Top