Home network help

[Ace]

Help!!!!!!!!!

My objective is to share a printer between two (2) desktop pc's , both
running XP sp2. The printer is an Epson Stylus Color 777. (Hopefully to be
replaced soon with Laser Printer???)

I purchased a Linksys printserver for USB with 4-port switch (Model PSUS4)
and EtherFast 10/100 LAN cards with corresponding Cat5e cables.

Thus far, I've been able to get the Printserver setup from one PC and print.
However, the 2nd PC won't find the printer during the Printserver setup.
Something about a cable not connected or ????

I'm thinking maybe the LAN card in 2nd PC may not be seated properly???
I've already swithced cables and plugged into different 'slots' of the print
server.

To digress a bit, I've found my McAfee Firewall has to be disabled in order
for the 1st PC to print. Ultimately, this is not acceptable. Is there a
solution where I can keep the firewall active? Both PC's have the McAfee
software.

Last, (maybe first???) is it necessary to set up a workgroup or something to
make the whole scheme feasable? Don't want to share internet connections,
but might want to transfer some files back and forth, or even play games
interactive.

Thanks in advance for your help,

Ace

 

[Kurt]

We'll need to know a few things. Does the print server give out IP addresses
to the PCs? Most do not. Generally, a router will do that. Otherwise, you'll
need to assign IP addresses manually to your PCs. You don't really need a
print server. Either one of the computers will function as a print server,
thoug it would have to be on for the other to print.

Let's start with a few basics.

First, XP Home or Pro?

Then:
From the command line on pc1, type "ipconfig /all > c:\pc1.txt
From the command line on pc2, type "ipconfig /all > c:\pc2.txt

Copy the files to a floppy and paste the contents of both files into your
reply.

....kurt

 

[Ace]

Kurt,

Thanks for your willingness to help. I've since gotten things to work.

I uninstalled the print driver from both PC's along with all the Printserver
software. Then re-installed print drivers on both PC's (which have XP
Home). Then reinstalled printserver on ONE PC only using their 'Setup'
wizard. (previously had tried installing on both). Followed instructions
more carefully and only used 'user setup' on 2nd PC. And it worked!

Though the instructions were there, they were rather obtuse, and only became
clear after a lot of failed attempts.

It doesn't help that XP home gives message that 'cable is not connected'.
Now, after I have the print server working, I realize the message about
cable not connected (message still appears) is referring to an Internet
connection between the 2 PC's, which I don't have nor want.

If you have any thoughts on why it takes so long to initialize the network
during bootup, I'd be interested to hear them.

Ace

 

[Kurt]

Odds are that the computers are set to auto-configure, which requires a
"DHCP" server. usually in a home network, the Internet router performs this
chore. Windows will wait a while and eventually time-out waiting for this
process to happen. After it gives up, Microsoft clients default to something
called "Automatic Private IP Addressing" or APIPA for short. In this case,
each computer randomly assigns itself an IP address on the 169.254.0.0
network. If there's a conflict (If something else already has that IP
address) it'll pic another one until it finds one that is unused. You can
speed things up by assigning the IP address manually. Normally, small
private networks use the 192.168.x.0 network, but you can use whatever you
want if you're not connected to the Internet. If you are connected to the
Internet, you'll need a private address.

Here's a good way to start:

Open a CMD window on both computers and type "ipconfig". Note the IP
Address, subnet mask and default gateway of each. Then go to the network
properties page on each computers (right-click "My network places", select
properties. Right-click "Local Area Connection", click properties. Click
"Internet Protocol (TCP/IP)" and then the "properties" button. Select "Use
these settings" (or whatever it is - the one instead of automatic settings).
Put in the same values as you read form the ipconfig. Then the computers
will just use those settings instead of waiting around for the DHCP server
to timeout.

....kurt

 

[Ace]

Kurt,

Thanks for your help. Did as you suggested below using IPCONFIG, etc and
all is well.

The addresses I got were both 169.xxx.xxx.xxx. Would there be any advantage
to setting them to 192.168.0.1 and 192.168.0.2 with subnet 255.255.0.0 ?

Ace

 

[Kurt]

If they're not connecting to the Internet no advantage. the 169.254.0.0
network has a subnet mask of 255.255.0.0 by default (it is in the class-B
range) so the total hosts are 65534, a lot of potential hosts for most home
networks. the 192.168.x.x is a class-C, so the default subnet mask is
255.255.255.0 and has 254 potential hosts. Most home-grade routers will only
route a "class-C sized" network and some will only route 192.168.something.
Other than that, one works as well as the other.

....kurt

 

[Ace]

Thanks again,

I'll leave well enough alone. Have a great day!