Flying Fox wrote:Can someone make any sense out of this?
drsauced wrote:That is weird. We have a Samsung printer so I feel your pain. It's actually working quite fine, probably the most trouble-free printer we have, just an oddball. The software finds the printer based on MAC address, so not IP based. You can assign it an IP from there, obviously. I'm going to say IP conflict?
The computers and printer are all 192.168.3.x, with netmask 255.255.255.0 typical of class C networks. Not too sure about CIDR vs classful. The computers are running Windows so can't do "/24" anyways. Printer's configuration screen is the same.Hz so good wrote:just for grins, can you share the IP/mask of the device? You doing CIDR vs classful?
That's the speculation (something messed up with ARP) we had after we got everything working. I have discounted 8 vs 8.1 since ping worked from B to printer. Now that stuff is working we are not going to go back and break it.Hz so good wrote:Did the printers MAC ever show up in A's ARP table? Think there's an issue with just Win8 as opposed to 8.1? I haven't used it much, so I dunno about what the changes were beyond the whole desktop boondoggle.
Since B can ping and print, to me that killed the theory of IP conflict?Hz so good wrote:drsauced wrote:That is weird. We have a Samsung printer so I feel your pain. It's actually working quite fine, probably the most trouble-free printer we have, just an oddball. The software finds the printer based on MAC address, so not IP based. You can assign it an IP from there, obviously. I'm going to say IP conflict?
You'd think it would've thrown an error, if there was a conflict. And wrkstn B *could* print from it, so...
Everything static IP, no computers with server OS.Hz so good wrote:Then I'd firmly affix my tinfoil hat and start looking around for a rogue DHCP server or something.
Fairly certain they are correct. Besides, how do you explain how B could ping A and B could print and ping to printer if the netmask is wrong?TwistedKestrel wrote:First thought would be wrong netmask on either A or the printer.
Captain Ned wrote:Ugh, printer problems. The primary cause of PTSD amongst competent sysadmins.
Flying Fox wrote:Everything static IP, no computers with server OS.
SuperSpy wrote:What's the error returned by the A -> Printer ping?
SecretSquirrel wrote:A bad netmask will cause issues like what you describe. If the printer's netmask was typo'd such that B was within the configured subnet and A was "outside" it, then the printer would send all responses to A to its configured default gate, if it had one. What is the last octet of the IP address of the two computers?
Users browsing this forum: DrJ and 7 guests