This is will be a new message but an old problem that was worked on before through this forum. Before you read on here, I encourage all who ant to help, please look at my prior two messages for a cursory look at the history of said problem. With that completed, please read on here:
1.) I figured out that a crossover cable really does not mean a USB to USB, but in reality, a regular old network cable. Duh, how we novices learn so much in such a long time!
2.) Have successfully mated a laptop running windows 8.1 x64 (Firefox browser, most recent release) directly to a Xerox Workcentre Pro 232 that is out of contract and out of development.I disabled WIndows Firewall for piece of mind as well. The main objective is and has been to access the CWIS. AND YES, HTTP/IPP is ENABLED. So trust me I have that covered. Secondary objectives include the ability to SCAN 11x17's.
3.) I am on the warpath of finding out why I cannot break into the CWIS, most of you believe at this point that the machine probably needs to be reset by a Xerox technician in order to gain access to the CWIS. But please realize that I picked up the copier for $300 at auction over a year ago now, in an effort to digitally scan my hand drawn artwork at 11x17 to help develop my business. And instead of paying Xerox $500 for a service trip, and running the risk the a technician not knowing any more that I do (prove me wrong), I will ever so be persistent in attacking this problem on my own BUT with deep appreciation of this forum and the talent on you all may have and are willing to share of course. And of course I am too stubborn to bring all my artwork to the local print house to be scanned there because that would make way to much sense. Stubborn can solve everything right? probably, no.
4.) I am now troubleshooting via direct crossover cable, have set the IP of the copier/printer (wannabe scanner) to 192.168.1.100 and my laptop (IPv4 to 192.168.1.101). Just downloaded the Global Driver for good measure as a first and fresh install on the laptop. I Downloaded Advanced Port Scannerv1.3, scanned and found it (the Xerox). But beyond that this program not so hot on the detail I need to understand the problem. Looked for variants of a port scanner and discovered this nice tool, Nmap-Zenmap GUI, this gets into the knitty gritty, and I will post the results of my first port scan here in a second.
5.) In summary it scans the ports of 192.168.1.100 and identifies 5 open/available ports, 1,5432,7000,7007,and 9100. And I feel like I am officially geeking out and I like it.
So now what? I know port 9100 is RAW and I am able to print through different devices on my network from different machines using that port.
Port 1 is construed as TCP and I think this is CWIS, correct me if I am wrong. No idea what 5432,7000,7007 mean. I think they are the OS on the drive? Firefox continues to tell me I can't have access. And with suggestion from another user here on the forum, I even downloaded and used Firefox V2 to side step the potential SSL certifications, but to no avail.
6.) Backing away from this again and sleeping on it from this weekend, is the CWIS actually on the hard drive or inside the copier? I was reading that the hard drive is mainly for temporarily holding files generated by the scanner or facisimile, and maybe this is confounding my problem a little bit. I bring this up because I wonder what a Xerox tech would actually do? Reset the hard drive? or reset the machine? Would the reset actually work and provide access to the CWIS?
7.) Another small analomy I am trying to understand is that the machine keeps redacting the Broadcast IP to 192.168.1.255 even though its actual IP is 192.168.1.100. If I leave it the communications with the machine appear just fine, coming up as XRX0000AA7B168E. When I go to the touchpad screen on the 232 and change it to 192.168.1.100 Broadcast, and port it again it comes up PIP-AG-XEROX232. It is strange.I think I know what AG is, when I purchased the machine at auction it came from the Agriculture Dept (Ag) at a nearby Tech school.
Last, I am debating on how else to communicate with the drive.I downloaded Knoppix and haven't done anything with it yet, but I am curious if this will help any with communicating with the Xerox in any way shape or form.
I tried Telnetting, that didn't work because port 23 is closed.
I am going to post my report from the Xerox and Nmap-Zen Map, here:
Thanks to all in advance of your efforts help solve this dilemma.
Solved! Go to Solution.
A crossover cable is not a regular internet cable, but it does look like one. To check them, hold the ends together, if the colors of the wires is in the same order, it is a Straight through network cable, if they do not, 2 colors are crossed over on the ends, it is a Crossover cable.
The implementation is typically as follows:
Crossover cables connect 2 devices directly, with no LAN to support them (Printer to PC, PC to PC)
Straight through will connect many devices together to make a network using a router or switch.
So, on your PC once connected with the Crossover to the printer, set the computers NIC to
IP=192.168.0.1, subnet to 255.255.255.0
On the printer set it to
IP=192.168.0.2, subnet to 255.255.255.0
If either requires a gateway to be set, use the IP of the other device.
2. Scan is not going to be possible with Windows 8 using SMB, possibly you could get it running via FTP, the printer is old and does not support SMB2 or 3, you don't need to understand this part, just believe it. If the machine supports scan to folder or mailbox, that may be much simpler.
3. The cable explains the inability to do this, if you need to use straight cables just grab a cheap router out of some friends junk pile and plug in the printer and the printer to it, set them both to DHCP and reboot, assuming the printer isn't broken, this will work nicely.
4. Print should be fine as long as you use RAW. In Windows 8, right-click the start menu and go to Control Panel > Devices and Printers, select Add Printer then select The Printer I want isn't listed.
Choose Add a local Printer > Create a new port > Standard TCP/IP port > Next
Enter as follows and do not have the box checked to Query
Click Next, wait for detection, if asked select the following exactly: Custom > Settings if not asked skip to after the image below.
OK > Next > Have Disk > Browse and go to the drivers location on the drive, which will be, if not exactly, C:\Xerox\X-GPD_5.433.6.0_PCL_x64_Driver.inf\ then just double click whatever single file is in there. Mine is x2UNIVL.inf
Click OK > Next > Replace the Current Driver > Next > Next > Do not share this printer > Next > Finish
Now, if you did not get prompted above to go into the port properties, do the following, fro the Devices and Printers list right-click on the Global Driver and select Printer Properties (Not Properties)
Select the Ports tab then Configure Port and get it set to exactly as shown here
5. Port 9100 confirms the above will work, but nothing else will, so print only per the above.
6. CWIS is in the firmware, the tech would wipe the device and set it to out of the box configuration, this is highly unlikely to be required, pretty sure your cable is the issue.
7. I have no idea, luckily Broadcast addresses have no use in this scenario.
Knoppix won't help do anything except break things, Xerox drives have Proprietary code. Good luck trying, but nothing you could do would resolve the issues you are seeing.
Telnet can be done on more than port 23, but since almost no ports are available due to your limited connection, and the fact you are very unlikely to be able to do anything useful at all, it isn't worth trying unless purely for educational purposes.
Hey thanks Joe:
The cable used came out of a old LinkSys box I had lying around.
So let's boil this down a little. I understand the difference between straight through and crossover, so that's good.
Set my expectation, I am not going to be able to access CWIS with a Windows 8.1 x64 system, period. T / F (True/False)
I can gain some or partial access to Scan via 'Scan to File' as a machine resource and manipulatting FTP? T / F
Your belief at this time is that I am utilizing a straight through network cable not a crossover cable. T / F
I have the ability to make my own crossover cable. T / F, ha ha this question is for me, YES I CAN by golly.
If I make my own crossover cable, and connect both machines, I'll be in heaven? T / F Conditions may apply? T / F
I am not going to be able to access CWIS with a Windows 8.1 x64 system, period. False
I can gain some or partial access to Scan via 'Scan to File' as a machine resource and manipulatting FTP? True
Your belief at this time is that I am utilizing a straight through network cable not a crossover cable. True
I have the ability to make my own crossover cable. T / F, ha ha this question is for me, YES I CAN by golly.
If I make my own crossover cable, and connect both machines, I'll be in heaven? T / F Conditions may apply? True for an odd sort of persons perception of the afterlife
Oh boy.... (sigh)....
I made a crossover cable, I connected of course, just as I did had with the straight through cable.
After following your instructions verbatim, I was not able to connect to the CWIS on the machine.
In desparation, I called up the derelicts of old machines I saved to prove Murphy's Law wrong, and attempted using PC's running Windows 7, another machine running Vista "Business" and my last hurray, the flavorable Windows XP Pro Service Pack 3 machine and attempted various connections crossover and straight through alike to no Avail.
This Xerox is kicking my you know what... I am entirely out of ideas, I have tried so many configurations, I've about lost all hope. Unless someonem out there would be so kind to analyze my postings and tell me where I left the wagon, or at the very least tell me with surety this machine is messed up.
I'm flabbergasted I cannot get into the CWIS, it confounds me why its so difficult.
Left side is an OEM crimp "O w/ WH, O, G w/ WH, B, B w/ WH, G, Br w/ WH, Br"
RIght side made by me "G w/ WH, G, O w/ WH, B, B w/ WH, O, Br w/ WH, Br"
I'm afraid that is just about as far as I can go.
If cables and settings and setup are all perfect, the only thing left is that the machine is corrupted, or set to block/disable all access.
If that is the case, the only remaining thing to do is reset the device.
The machine is ancient, it has no USB ports, the only way to even connect to it is via Serial cable, and with a software that is not available to download (Yay old proprietary setups!!!) And even if you had the software, you would need an old PC with a Serial port just to hook into it, so Windows XP or Windows 2000 would also be needed.
With no maintenance agreement, it would cost more than you have into the device in total at this point and there are no guarantees, you might have come upon the reason it was in the auction, it very easily could be broken beyond repair.
If you could find how to reset the machine NVM's you could likely get access assuming it is not actually physically broken, but you won't find that information here, even if I had it, I could not post it, but the internet is a vast place with many resources.
Sorry I'm a little late to the game, but I figured that I'd chime in and try to help, if I could. I was scouring the net trying to find some resolution on what to do with my WorkCentre 232 that I just inherited and yours is the only post that came up on the forums. Keep in mind, I only have the WC232...NOT the Pro version, but the machine is basically the same, just I have almost ZERO features on mine.
First of all, I read both of your threads, and while I can appreciate what you are trying to do, it can be very overwhelming if you're a beginner. The crossover cable that you made was not made correctly, but don't feel bad. It took me a while to get a handle on all of this stuff when I first started, too. Second, I read through everything you posted, and while you are on the right track, I think that you are missing a few steps. Let's just try to get you back on track...
Number 1: You do NOT need a crossover cable, a regular straight-through cable will be just fine.
Number 2: DO NOT just let your router assign an address (DHCP.) When you set the IP address on the WCP232 manually, you were spot-on. That means that no matter what addresses your router hands out to other devices, the WCP will always be the same, so all of the devices on your network know where to go to look for it. If you need clarification on how this works, I can give you an analogy if you'd like.
Number 3: Network is the best way to access the WCP. Don't worry about the USB, serial, and all that other stuff. And definately DON'T try to use Linux if you are not familiar with it. Windows will work just fine for you in this situation and any version will do.
Now, you said that you set the IP address of the WCP to 192.168.1.100 and your laptop to 192.168.1.101. That's fine, unless your router had already assigned the address 192.168.1.100 to something else. Then, you're trying to access the WCP, but when the request gets to your router, it might be forwarding it to the machine that has already been given that address, so your request is being denied. Verify the IP addresses being used on your network and make sure that you set the IP address on the WCP to something OUTSIDE of the DHCP range, then reboot your router, NOT the WCP.
When the router is back up and running, open your browser (Internet Explorer, Firefox, Chrome, or whatever) and enter the new IP address that you just set on the WCP into the address bar. When you do this, you should see the web interface for the copier come up on your screen. If you do, you've got it! To access most of the features, you will probably need the admin username and password for the WCP, but we can cross the bridge when we come to it. Just getting you TO the web interface at this point will be the goal for the day.
If you're still interested in getting this thing to work after all this, let me know and I can help you get the rest of the way (hopefully!) Good Luck and let me know!
My mistake: I did not see the picture clearly enough. Yes, the crossover cable that you made is correct. However, it is still not necessary. A regular, straight-through cable will be just fine and do the job nicely. Sorry about the confusion.