Cannot get network printer to work on Intel AP (W2K)

[cyberserious]

I cannot get the network printer to work over my Intel Anypoint home network. When I share the printer from the server PC, the Intel Sharing & Mapping software on the client PC is not flashing up "There's a new network printer..." and when I got into the Sharing & Mapping software there, my printer is appearing under "Unmapped printers" but when I attempt to share it, I get this error message:

"An error occurred while trying to connect to FRED/EPSON...Message: 1801"

I was unable to find documentation on this error at http://apsupport.intel.com/userWelcome.asp and there is no such error code as 1801 listed.

When I viewed the Intel error log, this is what I saw:

ERROR: Fri Jun 20 08:59:32 2003 (KEY=1)
DEBUG: UnMapNetworkPrinter(\\FRED\EPSON) dwResult=1223


ERROR: Fri Jun 20 09:24:38 2003 (KEY=1)
DEBUG: UnMapNetworkPrinter(\\FRED\EPSON) dwResult=1223


ERROR: Fri Jun 20 09:29:24 2003 (KEY=1)
DEBUG: MapNetworkPrinter(\\FRED\EPSON,) dwResult=1801


ERROR: Fri Jun 20 09:41:34 2003 (KEY=1)
DEBUG: MapNetworkPrinter(\\FRED\EPSON,) dwResult=1801


ERROR: Fri Jun 20 10:03:28 2003 (KEY=1)
DEBUG: MapNetworkPrinter(\\FRED\EPSON,) dwResult=1801


ERROR: Fri Jun 20 10:29:47 2003 (KEY=1)
DEBUG: MapNetworkPrinter(\\FRED\EPSON,) dwResult=1801


ERROR: Fri Jun 20 10:40:50 2003 (KEY=1)
DEBUG: MapNetworkPrinter(\\FRED\EPSON,) dwResult=1801


ERROR: Fri Jun 20 10:45:42 2003 (KEY=1)
DEBUG: MapNetworkPrinter(\\FRED\EPSON,) dwResult=1801

Fred

[jdharm]

A possibility:

Win9x doesn't like spaces in the share names. Check the Sharing tab in the printer properties on the server machine. Make sure that you have no spaces in the share name. Use hyphens or underscores if you really need some separation.

If you do change the share name then remove your previous install attempts from the client machines and try again.

Josh
<a target="_blank" href=http://www.jdharm.net>www.jdharm.net</a>

[cyberserious]

I don't have any spaces in either share name, and both computers have Windows 2000.

Fred

[jdharm]

Hmm. I wonder where I got Win9x from? /images/forums/icons/blush.gif

Is this a wireless network or the phone line network?

Josh
<a target="_blank" href=http://www.jdharm.net>www.jdharm.net</a>

[cyberserious]

Upon searching in regedit, I discovered something that might be part of the problem.

Here's what appears to be a bunch of invalid keys I discoverd in regedit. I have only one of these devices, but I found multiple instances of the following:

Intel(R) AnyPoint(TM) PCI 10 Mbps Phoneline Adapter

Intel(R) AnyPoint(TM) PCI 10 Mbps Phoneline Adapter #3

Intel(R) AnyPoint(TM) PCI 10 Mbps Phoneline Adapter #6

This could be what's causing some of my problems. Should I manually delete all the ones with #3, etc..?
Fred

[cyberserious]

Josh,
Opps, I failed to mention that yes, it is a phoneline network. My Server PC is using the internal PCI card, while the Dell laptop is using the external USB adapter.
Thanks,
Fred

[jdharm]

Well, at this point I am going to bow out of the discussion. I don't know anything about the phoneline equipment and networking, so I would just be making stuff up if I went on.

About those keys: I wouldn't delete them. I have multiple entries like that on my notebook. It is a result of changing network configurations several times. Each change is considered a new network and new entries are created for it, even though I have the same hardware each time. I wouldn't think it would be causing a conflict, but I could be wrong (see statement above).

As I leave I might leave you with a suggestion. Go to Ethernet. The phoneline stuff was for a time when ethernet equipment was too expensive for individuals or running new wires was not possible. Now ethernet equipment is dirt cheap and running new wires is not necessary with wireless. With only two computers you could network them together with a cross cable for about $15 or set up a wireless network for under $100 (after rebates /images/forums/icons/smile.gif).

Josh
<a target="_blank" href=http://www.jdharm.net>www.jdharm.net</a>

[cyberserious]

I could always go the eithernet route, but then I'd have to hire somebody to climb though the attic and drill holes in the walls to install the cable.

I have thought about wireless, but I'm concerned about privacy and have health concerns about prolonged exposure to high-frequency RF energy, for Cancer, etc..

One big problem with the Intel product I'm using is it has been discontinued, therefore is no longer supported.
Fred