Thread View: comp.dcom.modems.cable
4 messages
4 total messages
Started by Alan Sadler
Sun, 07 Nov 1999 00:00
New Cable Modem setup & network printer
Author: Alan Sadler
Date: Sun, 07 Nov 1999 00:00
Date: Sun, 07 Nov 1999 00:00
22 lines
1693 bytes
1693 bytes
There's good news and bad news. Yesterday 21st century/Chicago exchanged my POS Zenith cable modem with a new Nortel. The speeds almost doubled, from 4-600bps, to consistently 900-1100bps. Not too bad. The bad news is, that my printer stopped working. It's an old HP3, connected to a HP Jetdirect EX plus print server. The printer is too far for a printer cable, so I hooked it up through Ethernet. It worked for the last 5 months without a hitch. I didn't check it before the 21st century installer left. He did say that my IP is now Dynamic(DHCP) instead of the static one on the old modem. I understand the above, but not why the Printer stopped working. Any help would be appreciated. Also, Another slightly disturbing change is that I can see the world in my Network Neighborhood. Most machines are not shared or drives are password protected. Thankfully, I can't get see my machine. What is the proper protocol? Should I just mind my own business, or somehow inform the user that I can see their most intimate files? Thanks in advance for you reply. -- Alan Sadler <sadler@BigDeahl.com>
Re: New Cable Modem setup & network printer
Author: David Gibbs
Date: Sun, 07 Nov 1999 00:00
Date: Sun, 07 Nov 1999 00:00
34 lines
2487 bytes
2487 bytes
Caveat: I'm not a networking or cable modem expert ... the following is just from my own experience. On Sun, 7 Nov 1999 12:05:36 -0600, "Alan Sadler" <asadler@21stcentury.net> wrote: >The bad news is, that my printer stopped working. It's an old HP3, >connected to a HP Jetdirect EX plus print server. The printer is too far >for a printer cable, so I hooked it up through Ethernet. It worked for the >last 5 months without a hitch. I didn't check it before the 21st century >installer left. He did say that my IP is now Dynamic(DHCP) instead of the >static one on the old modem. I understand the above, but not why the >Printer stopped working. Any help would be appreciated. Sounds like your printer is no longer in the same network as your computer. When you had a static IP you could setup the printer server to have a similar IP address as your computer... now the IP address is set by the DHCP server and is probably not in the same network as the printer. Assuming you are running windows... run the WINIPCFG program to see what IP address is assigned ... a wild guess is that the IP is in the 24.x.x.x region (this is a standard address block for the cable industry). Your printer is probably NOT in this area. A solution would be to put a 2nd NIC into your computer and hook the cable modem to that, so it will have it's own IP address assigned by DHCP ... and assign private IP's to original NIC, and plug that into the hub with your print server (and any other computers). That also gives you the ability to make your cable modem attached computer act as a router (with appropriate software) so that all the computers in your network can access the internet via your one connection. david
Re: New Cable Modem setup & network printer
Author: Rolf Ostergaard
Date: Sun, 07 Nov 1999 00:00
Date: Sun, 07 Nov 1999 00:00
54 lines
3250 bytes
3250 bytes
Alan, What Dave wrote is very likely the case. The ethernet print server is yet another reason that a cable modem should be a router and not a bridge - unfortunately the cable industry think they loose control (= money) that way. Unless you want to install more hardware, you should convince your provider that they need to give you an extra IP address for your print server. Request that you get it for free, even if they normally charge for it. In this case you are not hooking up an extra PC (= extra user), so they should give it to you for free. Good luck, -- http://www.Cable-Modems.Org/ is your cable modem reference guide. Tutorial, Q&A, articles, home networks, security, photo gallery and more! David Gibbs wrote in message <18QlOOA8+yZu9Re=o5JGhTX32svf@4ax.com>... >Caveat: I'm not a networking or cable modem expert ... the following >is just from my own experience. > >On Sun, 7 Nov 1999 12:05:36 -0600, "Alan Sadler" ><asadler@21stcentury.net> wrote: > >>The bad news is, that my printer stopped working. It's an old HP3, >>connected to a HP Jetdirect EX plus print server. The printer is too far >>for a printer cable, so I hooked it up through Ethernet. It worked for the >>last 5 months without a hitch. I didn't check it before the 21st century >>installer left. He did say that my IP is now Dynamic(DHCP) instead of the >>static one on the old modem. I understand the above, but not why the >>Printer stopped working. Any help would be appreciated. > >Sounds like your printer is no longer in the same network as your >computer. When you had a static IP you could setup the printer server >to have a similar IP address as your computer... now the IP address is >set by the DHCP server and is probably not in the same network as the >printer. > >Assuming you are running windows... run the WINIPCFG program to see >what IP address is assigned ... a wild guess is that the IP is in the >24.x.x.x region (this is a standard address block for the cable >industry). Your printer is probably NOT in this area. > >A solution would be to put a 2nd NIC into your computer and hook the >cable modem to that, so it will have it's own IP address assigned by >DHCP ... and assign private IP's to original NIC, and plug that into >the hub with your print server (and any other computers). That also >gives you the ability to make your cable modem attached computer act >as a router (with appropriate software) so that all the computers in >your network can access the internet via your one connection. > >david >
Re: New Cable Modem setup & network printer
Author: Mike Stucka
Date: Sun, 07 Nov 1999 00:00
Date: Sun, 07 Nov 1999 00:00
21 lines
1803 bytes
1803 bytes
I think the other folks hit on some great ideas. The static IP likely would be the most permanent, and best fix. Other possibilities include: Using a different protocol, e.g., ipx/sp, for your printer if its Ethernet card supports it. That way, whatever your computer has to do with TCP/IP traffic won't affect the printer at all. This sucks for a couple reasons. Alternately, see if there's a way to "multihome" your PC's Ethernet card. This involves assigning multiple IP addresses to the very same interface (card). This has a couple benefits, including the ability to let you add your own logical network behind the scenes at will. If your operating system can do it (check the vendor's home page, search for it), this would be -great. In the future, for example, you could add a second PC and use something like a wingate-style proxy to get that one on the Internet as well. IT also keeps you from having to go through AtHome when you have problems internally; they simply become your problem. Mike
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads