I used to when I was a kid and built plastic model airplanes. I remember it being much easier to paint with an airbrush, but the thing was a pain in the ass to clean.
Yeah I suppose cleaning it would be a pain. I can get a pressure regulator for my large compressor for about $20 and another $20 for a basic gun. Or I can get a portable compressor gun combo for $100. Dealing with the large compressor limits me to the garage though. What kind of paints did you use?
Here is one for bfun to answer if he can because I don't understand it. Head office Copier (192.168.0.7) keeps cutting in and out on network. Windows ping will often fail and as a result can't scan from or print to it. Linux ping will always work. Do a network sweep and get different MAC address on 192.168.0.7 than one assigned to copier. Trace MAC address to 192.168.0.92 Find this IP in arp table on core switch assigned to port A1 (arp -a results on linux show odd results for 192.168.0.7 and 192.168.0.92) Port A1 is ADSL router with no other ethernet cables attached Check all devices attached wirelessly to router and find a Samsung Galaxy SII with 0.92 Disable its wifi and hey presto, canon copier comes back to life. DHCP range is 192.168.0.51-192.168.0.200 so can't have even tried to pick up address from Windows Server. Any ideas what the hell has gone on here because I am at a loss to explain it and now the person cannot connect their phone to the network.
Whats the mask on those networks? That DSL router doing it's own DHCP or does it forward the DHCP to the Windows server? It's all a bit confusing but sounds like you might have the same network advertised on the DSL router and the WIn DHCP server. The DSL routers probably use 192.168.x.x by default. The only time I see LAN flapping is from duplex or speed mismatches. If the same IP is assigned to multiple devices you'll see routing and switching oddness. Have you checked the switch logs? Out of curiosity can you do multiple trace-routes and see what happens?
Subnet mask 255.255.255.0 (/24) DHCP is disabled on the router and it is handled by Windows Servers. The ADSL router does have routing tables to other subnets but other than it is just used as a gateway to the internet. It is only this one device that is causing a problem, everything else that connects via wireless is fine. The only odd thing about the Galaxy SII is that it seems to have some sort of web server built in as you can access it via its IP address to manage the phone and its the only culprit I can think of. Why is should affect a specific device outside of the DHCP scope is beyound me. Any traceroute I do just resolves the IP on the first hop as everything outside of the blade enclosures are connected via a single HP procurve zl series switch. Other than high collisions being detected on port D8 the log contains nothing other than interfaces going up and down when PC's go online/offline.
I think I'm missing something. Looks like they are in the same scope. The printer is 192.168.0.7 and the Galaxy is 192.168.0.92.
The scope is 192.168.0.50 to 192.168.0.200, 1-49 and 201-254 are outside the scope and used to assign static addresses to printers, servers etc.
So does this look about right? Just for fun can you assign a static IP to the copier? Something different than 192.168.0.7
For the purposes of this investigation yes, the DHCP server is a VM on a blade connected to the core switch via the blade switches which are connected to the core switch through what I believe is called a pair of 4 gig trunk channels but lets not make the plan too complicated... I will try to change its IP tomorrow. That copier (Canon iR 5185) is a pain when it comes to changing the IP configuration, it takes it a long time to reboot which is needed to update the config and even then it takes it 5 minutes to bring the IP config back up. Because its in a production environment changing too much during main hours might be difficult but I am working Saturday so if worst comes to the worst I will fiddle with it then. It is used quite heavily for copying, printing, emailing and scanning for OCR so if it is down for even 30 minutes I get grief. It also has a computer attached directly to it running some software called eCopy which I believe is configured to find the copier via its IP so I would like to leave it on 0.7 where possible. We have two other Canon iR copiers on the same subnet (one of them with ecopy) and neither of them have shown the same symptoms. One of them is 0.8 so I may try swapping the IP's around. As a side point I need to get some good software to draw up our head office network on some sort of map/plan. All the network monitoring software I have makes a complete mess of it when trying to do it itself as we have a public network consisting of a big HP switch, 2 blade switches, ADSL router, a fibre transceiver going to our corner office attached to 2 x 3COM switchs at the other end and a CISCO wan router attached to 2 fibre connections going to other branch offices. Then a private network between the blades and the SAN again with a HP switch in the middle for the iSCSI connections for the VM's. Any recommendations of something cheap or even free?