Using a Linksys EFSP42 under Windows XP Home and Pro

[DarkGemini]

Ok, so I've been going crazy getting this stupid thing to work in
WinXP... and I got it. Here's what you need to do...

- Install the IPX/SPX and NetBEUI networking protocols in XP. The
latter can be found in the valueadd folder on the XP CD.
- On one of the CD's that comes with the EFSP42, there's a utility
called BiAdmin. Install it.
- Using the BiAdmin utility with all 3 protocols checked, it will
search for the Print Server. Once found, it will list in the window
on the right. Select it, and click on the TCP/IP button. (It looks
like a Yellow cloud, more or less)
- Click the Fixed IP Address radio button, and enter the appropriate
network information, ie. 192.168.1.69 for the IP, 192.168.1.1 for the
gateway, 255.255.255.0 for the subnet, and so on.
- Write this information down. You'll need it later.
- Click Save to Device.
- Open the Printer and Faxes control panel. Select the Add New
Printer wizard.
- When asked how the printer is connected, choose "Local Printer
Attached to this Computer" and uncheck "Automatically detect and
install" and hit next.
- Click "Create new port" and select "Standard TCP/IP" as the type.
- When asked to enter the IP, enter the IP of the EFSP42, and hit
next.
- Choose Custom device type, and hit the Settings button. Choose the
LPR protocol, and choose L1 or L2 as the queue name, depending on the
connected port. Hit OK, then next. Hit finish, and finish installing
your printer to the computer (drivers, etc.). If the drivers are
already installed, then all you need to do it add a new port using
these instructions.

If anyone has any input to abbreviate these instructions, or has a
better idea altogether, definitely post a reply. To anyone this may
help, I feel your pain. Good luck.

 

[Chuck]

Ok, so I've been going crazy getting this stupid thing to work in
WinXP... and I got it. Here's what you need to do...

- Install the IPX/SPX and NetBEUI networking protocols in XP. The
latter can be found in the valueadd folder on the XP CD.
- On one of the CD's that comes with the EFSP42, there's a utility
called BiAdmin. Install it.
- Using the BiAdmin utility with all 3 protocols checked, it will
search for the Print Server. Once found, it will list in the window
on the right. Select it, and click on the TCP/IP button. (It looks
like a Yellow cloud, more or less)
- Click the Fixed IP Address radio button, and enter the appropriate
network information, ie. 192.168.1.69 for the IP, 192.168.1.1 for the
gateway, 255.255.255.0 for the subnet, and so on.
- Write this information down. You'll need it later.
- Click Save to Device.
- Open the Printer and Faxes control panel. Select the Add New
Printer wizard.
- When asked how the printer is connected, choose "Local Printer
Attached to this Computer" and uncheck "Automatically detect and
install" and hit next.
- Click "Create new port" and select "Standard TCP/IP" as the type.
- When asked to enter the IP, enter the IP of the EFSP42, and hit
next.
- Choose Custom device type, and hit the Settings button. Choose the
LPR protocol, and choose L1 or L2 as the queue name, depending on the
connected port. Hit OK, then next. Hit finish, and finish installing
your printer to the computer (drivers, etc.). If the drivers are
already installed, then all you need to do it add a new port using
these instructions.

If anyone has any input to abbreviate these instructions, or has a
better idea altogether, definitely post a reply. To anyone this may
help, I feel your pain. Good luck.

Did you previously post here for help? I can't find any posts under your
current nym DarkGemini. If you had, it would be very interesting to see what
error analysis you had done.

To start, on any properly working Windows LAN, you need neither NetBEUI nor
IPX/SPX. Windows networking is designed to use TCP/IP, with NetBIOS Over TCP/IP
(NBT) as an interface.

If you have file sharing (Client for Microsoft Networks / File and Printer
Sharing for Microsoft Networks) bound to both IPX/SPX, NetBIOS, and TCP/IP
(NBT), you have complicated your network needlessly. Having file sharing bound
to multiple protocols may mean longer timeouts when searching for named
resources, as a named resource query may search thru all protocols if a resource
isn't immediately found.

Here is an interesting article about the different protocols that you have added
to your LAN:
http://www.practicallynetworked.com/sharing/xp/network_protocols.htm

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[DarkGemini]

Did you previously post here for help? I can't find any posts under your
current nym DarkGemini. If you had, it would be very interesting to see what
error analysis you had done.

To start, on any properly working Windows LAN, you need neither NetBEUI nor
IPX/SPX. Windows networking is designed to use TCP/IP, with NetBIOS Over TCP/IP
(NBT) as an interface.

If you have file sharing (Client for Microsoft Networks / File and Printer
Sharing for Microsoft Networks) bound to both IPX/SPX, NetBIOS, and TCP/IP
(NBT), you have complicated your network needlessly. Having file sharing bound
to multiple protocols may mean longer timeouts when searching for named
resources, as a named resource query may search thru all protocols if a resource
isn't immediately found.

Here is an interesting article about the different protocols that you have added
to your LAN:
http://www.practicallynetworked.com/sharing/xp/network_protocols.htm

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

IPX/SPX and NetBEUI were added so that the BiAdmin program could find
the print server. Whether or not they are required for the program to
locate the print server remains to be seen.

However, once the server is setup and running, they can be removed,
since the server is located by IP address, which is a function of
TCP/IP. Should've included that bit in my original post; sorry if it
caused any confusion.

And no, I've never posted here. However, there have been more than a
few individuals that have had similar experiences trying to use the
EFSP42 under WindowsXP, so I thought I'd post my experiences. Problem
is, I don't quite remember where I saw those posts, and didn't have
time to search them out when I came across this solution.

 

[Chuck]

IPX/SPX and NetBEUI were added so that the BiAdmin program could find
the print server. Whether or not they are required for the program to
locate the print server remains to be seen.

However, once the server is setup and running, they can be removed,
since the server is located by IP address, which is a function of
TCP/IP. Should've included that bit in my original post; sorry if it
caused any confusion.

And no, I've never posted here. However, there have been more than a
few individuals that have had similar experiences trying to use the
EFSP42 under WindowsXP, so I thought I'd post my experiences. Problem
is, I don't quite remember where I saw those posts, and didn't have
time to search them out when I came across this solution.

Yeah you're right - some network devices need to be discovered first, and bare
TCP/IP isn't a great protocol for discovery. I've worked with print servers
before, and they do need to be discovered, before the TCP/IP address can be set.

We ended up setting up a dedicated LAN with one computer running IPX/SPX, for
the sole purpose of setting up the print servers for TCP/IP. So much faster
than discovering a single IPX/SPX device on a 500 computer LAN, repeatedly for a
couple dozen servers. With a couple computers and one server, the difference
becomes a bit less significant.

I wonder where NetBEUI enters the picture?

But it was good of you to share your experience. Who knows how many high blood
pressure tablets may not be necessary cause you shared your knowledge.

I know that GMail contains copious anti-spam remedies. But some GMail users
have reported frustration in trying to delete large volumes of unwanted email -
which will accumulate, if you don't delete it regularly. And the more you
advertise your address, in places like this forum, the more unwanted email
you'll get.

It's to everybody's benefit if you learn to munge your email address properly,
and keep yourself a bit safer when posting to open forums. Protect yourself and
the rest of the internet - read this article.
http://www.mailmsg.com/SPAM_munging.htm

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.