Bad network connection

[rrrohan]

I have a C308 with glitchy network

It can print ok

It can scan to SMB ok

But scan to Office365 via direct send fails. 4 other copiers on site use identical settings and work fine.

Also if i put on DHCP it fails to obtain a IP. Laptop connected on same port with same cable works fine obtaining IP

I cant access copiers web interface/remote panel or access it via data admin.

Ping drops about 15% of the time

Ping using laptop on same port works with no drops.

I did a network settings reset in service mode but it didnt help.

Is it time for a MFPB?

[allan]

Re: Bad network connection

Does it have the latest and greatest firmware?
Any CFA14 or CE301 in the history?
Have you done self diagnostics on it?

[Synthohol]

Re: Bad network connection

Set the network speed to 100 speed duplex.
I find most routers now autonegotiate the speed.
Modern nic cards in copiers do the same.
Sometimes they can't agree on a speed and ignore each other.
Also a network initialization can help.

[copier tech]

Re: Bad network connection

I have a C308 with glitchy network

It can print ok

It can scan to SMB ok

But scan to Office365 via direct send fails. 4 other copiers on site use identical settings and work fine.

Also if i put on DHCP it fails to obtain a IP. Laptop connected on same port with same cable works fine obtaining IP

I cant access copiers web interface/remote panel or access it via data admin.

Ping drops about 15% of the time

Ping using laptop on same port works with no drops.

I did a network settings reset in service mode but it didnt help.

Is it time for a MFPB?

If your laptop connects fine then most likely the copier is OK.

Can you wheel the machine & swap it with another copier you say is working fine? This will confirm it's not the wall LAN socket or switch etc the copier is connected to.

[bsm2]

Re: Bad network connection

Have you tried changing the Ip address to a new one yet?

[BillyCarpenter]

Re: Bad network connection

I have a C308 with glitchy network

It can print ok

It can scan to SMB ok

But scan to Office365 via direct send fails. 4 other copiers on site use identical settings and work fine.

Also if i put on DHCP it fails to obtain a IP. Laptop connected on same port with same cable works fine obtaining IP

I cant access copiers web interface/remote panel or access it via data admin.

Ping drops about 15% of the time

Ping using laptop on same port works with no drops.

I did a network settings reset in service mode but it didnt help.

Is it time for a MFPB?

Based on what you're saying, it points to a bad NIC. But like Synthohol suggested make sure that the copier is set on the correct speed setting for the network it's on. You may also want to try another port on the switch.

[emujo2]

Re: Bad network connection

Scan to SMB and printing work, but you suspect a NIC??? 1st off what is the reason for the failure? Login error, server connect?? Office 365 is a finicky beast..Before you go spending $$$ on control boards..Check SSL settings, DNS and domain settings, from address, gateway (this would be my prime suspect as internal comms seem to work but getting to Office365.com fails). Have you done a Tracert to the offic 365 server? Do your ping statistics include a laptop directly connected to the MFP or just over the network?? E

[BillyCarpenter]

Re: Bad network connection

Scan to SMB and printing work, but you suspect a NIC??? 1st off what is the reason for the failure? Login error, server connect?? Office 365 is a finicky beast..Before you go spending $$$ on control boards..Check SSL settings, DNS and domain settings, from address, gateway (this would be my prime suspect as internal comms seem to work but getting to Office365.com fails). Have you done a Tracert to the offic 365 server? Do your ping statistics include a laptop directly connected to the MFP or just over the network?? E

He says he can't pull an IP address using DHCP for the copier but when he hooks up his laptop that he can.

[Phil B.]

Re: Bad network connection

He says he can't pull an IP address using DHCP for the copier but when he hooks up his laptop that he can.

doesn't sound like a NIC problem to me ... sounds like restrictions set by NA, and possibly a flakey router. The fact that it prints/scans ok tells me that the NIC is ok.. and the fact that the laptop works fine is another indication.

the fact that OFFICE365 isn't playing well it direct link to the flaws in O365. We have had problems all over the world with Bill's crappy software,

from the Win10 updates changing settings... down to the WSD shit they push if you aren't careful.

Gates and MS have been screwing the world for decades.

[BillyCarpenter]

Re: Bad network connection

doesn't sound like a NIC problem to me ... sounds like restrictions set by NA, and possibly a flakey router. The fact that it prints/scans ok tells me that the NIC is ok.. and the fact that the laptop works fine is another indication.

the fact that OFFICE365 isn't playing well it direct link to the flaws in O365. We have had problems all over the world with Bill's crappy software,

from the Win10 updates changing settings... down to the WSD shit they push if you aren't careful.

Gates and MS have been screwing the world for decades.

Maybe I'm reading this wrong. He says he can't obtain an IP address via DHCP and that ping is dropping 15% on the copier but no loss on his laptop. And no DHCP on copier but works fine with laptop. Doesn't make a lot of sense to me unless something is going on with the NIC. There are no variables other than the Copier and Laptop.

But if he's able to print and scan and he's having no problem, I wouldn't worry about it. He just needs to figure out Office365.

[bsm2]

Re: Bad network connection

Its called a clue

I cant access copiers web interface/remote panel or access it via data admin.

[Phil B.]

Re: Bad network connection

Maybe I'm reading this wrong. He says he can't obtain an IP address via DHCP and that ping is dropping 15% on the copier but no loss on his laptop. And no DHCP on copier but works fine with laptop. Doesn't make a lot of sense to me unless something is going on with the NIC. There are no variables other than the Copier and Laptop.

But if he's able to print and scan and he's having no problem, I wouldn't worry about it. He just needs to figure out Office365.

the NA can set 'permissions' on ANY device on his network. I have run into this before, they set a static address and turn off DHCP abilities. He

hasn't declared if he has checked to see if the NA has made those exclusions ... hell he hasn't really told us if he has checked the network end at all,

just that he can use DHCP from his lapper but not from the network.

Think about it.. IF he can pull DHCP from his lapper, but not from the connected network how can it be the copier? if it works on the lapper it

HAS to be network related.

[bsm2]

Re: Bad network connection

Another Clue it's impossible to pull a DHCP address
using a just a laptop.
Copier would timeout as A laptop CAN'T assign an Ipaddress.

Copier would have a set static ipaddress as well as the laptop.

Lets ALL wait for the Tech to reply with more information

[BillyCarpenter]

Re: Bad network connection

the NA can set 'permissions' on ANY device on his network. I have run into this before, they set a static address and turn off DHCP abilities. He

hasn't declared if he has checked to see if the NA has made those exclusions ... hell he hasn't really told us if he has checked the network end at all,

just that he can use DHCP from his lapper but not from the network.

Think about it.. IF he can pull DHCP from his lapper, but not from the connected network how can it be the copier? if it works on the lapper it

HAS to be network related.

I see what you're saying, I THINK. You're saying that if the NA has reserved an IP address for the copier that it's gonna always default to that IP address via the Mac Address of the NIC of the copier and not pull an IP Address. No? Yeah? lol

[BillyCarpenter]

Re: Bad network connection

Phil,

I just went to my virtual lab and I see what you're saying. From Windows Server 2019, I can exclude any device from obtaining a DHCP address by entering the MAC Address of said device. Never thought about that. Good call.