IP-cocktail, packet losses

[Hansoon]

Had to set up a MFP these days and did as follows:

Using ipconfig it showed that the workstation had two nics's 10.132.136.3 and 10.139.115.10 so obviously each serving a segment (physical and/or logical I could not establish due to my lack of experience). Since other printers where connected to that workstation using the 10.132.136.xxx range I used Angry-IP-Scan to find an unused address there. However, IP-Scan in the latest beta version is showing automatically the IP-address of the workstation as a default and was giving me 10.220.0.5, WTF? So now we are having three segments? Why didn't give ipconfig or ipconfig /all me this 3rd IP-range?

Than I tried to hook-up the MFP by using the unoccupied 10.132.136.100 address. I could establish a connection, make a testprint and was able to see the web interface of the copier but with some delay. That's why I made a ping and was surprised to see packet losses of 50-75% and even sometimes a 100% loss.

Expecting a router causing this, I used tracert but it showed a direct connection between 10.132.136.3 the workstation and 10.132.136.100 the MFP, without any other nodes inbetween.

Question1:
Why are only two segments visible with ipconfig although obviously three with Angry-IP-Scan are present?

Question2:
Any explanation for the packet loss? I changed already the controller and NIC of the MFP with the same resuslts.

Hans

[unisys12]

Personally, I would enable DHCP on the MFP and then program in the gathered info through a Static IP.

On Ricoh MFP's, this means leaving DHCP enabled at boot. Then after verifing that everything works properly, print out a config page and switch the network interface over to Static and copy all the info over manually.

A lot of folks will say that this is a bad idea, but if you really pay attention to the DHCP server (be it a switch or server) you will find that it assigned an address and that is that. It will not reassign that address until it runs out and has to find new addresses. It will then rescan the assigned subnet and find unassigned addresses and take over, again, from there.

Without knowing that you have a quality address... I would start over from scratch using the method above. If you cannot, then I would start by manually pinging IP's within the same subnet as the PC's, to find a free IP. At the point you find one, I would program it in as a Static IP and ask for the rest of the info needed.

Our dealership does have one account that uses a seperate subnet for all their printers/MFP's. In this case, the above method will not work, because the MFP will pull an IP from the subnet for the PC's. This will not help you or your sys admin at all.

Also, in a large network or WAN, pay special attention to the subnet mask! This can play a very important part of your network picture also!

Again, I would see what my MFP pulls and compare that to what the client wants. This can tell you a lot!

[cobiray]

If the customer has this much going on the the network (different subnets, multiple network connections) the customer has to have an IT staff on hand, don't they? Often, I can get an IP and keep it in a range that they like.

I too have used the DHCP trick to grab an IP off of the network. Just macke sure you remember to change it to static before you leave. I hear it might get you a call back...

With 95% of our equipment going out as MFP's, we have devised a digital needs analysis form that is (allegedly) filled out by the sales rep before the machine goes out. This entails contacting the customer and talking to the customers IT staff, getting an IP, subnet and gateway address, and determining what MFP functions they will be using (printing, scan to folder, scan to email, fax forward, etc.) This, in theory, allows the install person/team to have most of the information going into the account and they can have as much info and setup done on the equipment before it rolls in the door. Granted, there are always exceptions to the rule (un informed customers, "I forgot to call about that" or whatever) but it really helps cut down on the time it takes to complete the installs when the info is filled in and accurate. Just thought I'd share how we're attempting to tackle a situation that can be a pain in the neck.

[Hansoon]

.
Very good info guys, lots of thanks.

we have devised a digital needs analysis form

You have an example for me please? Thanks.

Hans

[FRIDGEMAGNET]

Question2:
Any explanation for the packet loss? I changed already the controller and NIC of the MFP with the same resuslts.

Hans

Hi Hans
What network speed is the MFP set to? I have seen this when it is set to "Auto". Try setting to 10mb fixed or 100mb fixed (check actual network speed first - it may be either).

[Hansoon]

Hi Hans
What network speed is the MFP set to? I have seen this when it is set to "Auto". Try setting to 10mb fixed or 100mb fixed (check actual network speed first - it may be either).

Interesting idea, thanks for that. I will go there next week and see if this will bring something cause its set at "Auto" indeed.

Hans

[Scott_Lewis]

Using a static IP in a DHCP environment

Most of what I've been reading is good advice. I just want to throw out a few thoughts on using a static IP address picked up from a DHCP server.

The 'proper' way to do this is to have the assigned IP address reserved to the MAC address of the copier in the DHCP server. This will only work with more sophisticated DHCP servers. AFAIK, most of the light weight routers with DHCP built in will not be able to handle this. You would be better served to manually select an IP that is outside the range of addresses that the server assigns. ALL DHCP servers that I've come across will set aside a range of addresses it will not assign and can be used without fear of it being assigned to another device.

Here is the problem with using an IP address previously assigned by the server......... Whenever the copier is turned off, the server can and will assign that address you put into the copier. When you turn that copier back on, guess what, some other device is now using your address. So long as the MFP is always running, the server will know that the IP address in the MFP is not available. (The server will always check to see if any device is using an IP address, per protocol for DHCP, before assigning that IP address to any device.)

Bottom line, use an address that will never be assigned by the server OR reserve that IP in the DHCP server to the MFP (usually by MAC addresss).

[PaulLoveless]

Just wanted to second the thought process of statically assigning a DHCP pool address. Works well for me in cases where I don't have predetermined IP addresses.

[TheOwl]

If your MFD is setup correctly, you don't even have to use the IP Address in the TCP/IP Port.

If your DNS and in some cases, DDNS is setup correctly, type in the MFD's host name. That way it doesn't matter when it changes the IP address as the DNS service running on the network will resolve the name to the IP address. This will also work for the Web Interfaces.

I agree with the other replys that a DHCP Reservation is the way to go, but this method can also help out if you can't get access to routers, servers and so on.