Re: Win 98SE Machine cannot see printer on home network
From: Chris Severance (sNeOvSePracMh3ONE@hotmail.com)Date: 02/28/02
- Next message: Carlos: "IPTABLES PROBLEM"
- Previous message: Chris Severance: "Re: Packet Sniffing & Spyware"
- In reply to: The Silent Observer: "Re: Win 98SE Machine cannot see printer on home network"
- Next in thread: The Silent Observer: "Re: Win 98SE Machine cannot see printer on home network"
- Reply: The Silent Observer: "Re: Win 98SE Machine cannot see printer on home network"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: Chris Severance <sNeOvSePracMh3ONE@hotmail.com> Date: Wed, 27 Feb 2002 21:15:28 -0500
On Wed, 27 Feb 2002 04:21:35 GMT, The Silent Observer
<silent1@ix.netcom.com> wrote:
>Chris Severance wrote:
>
>> On Tue, 26 Feb 2002 04:28:12 GMT, The Silent Observer
>> <silent1@ix.netcom.com> wrote:
>>
>>
>>>I don't know for certain if the XP machine is sharing on TCP/IP or
>>>IPX/SPX -- I have (of course) both protocols on all the machines on the
>>>network, one to share on and the other for Internet functions, and I'm
>>>not sure how to tell which protocol is being used for a given
>>>connection.
>>>
>>
>> Right Click My Network Places | Properties | Advanced | Advanced
>> Settings.
This will take you to where you can tell XP or 2K what protocols on
what interfaces it is to be using for File & Print. A casual glance
will tell you what's possible. I am on Windows 2000 and can't get to
an XP machine so your wording and placement may be slightly different
but it's all there.
>I've got both protocols installed -- TCP/IP is required to do anything
>on the Internet, of course, and I figured I'd need to have IPX/SPX in
>order for the XP machine to see the shares on the two 98 systems.
>Unfortunately, it still doesn't see those, apparently because the XP
>firewall blocks that.
I have already had IPX networking shares between XP, 2K, and 9x
machines. It works just fine but is a bit slower at browsing than I
tolerate. Things you need to check if it isn't working for you.
1. Make sure IPX is bound to Client for M$, File & Print on all
computers.
2. Make sure IPX is using the same protocol. I use 802.2 myself
because that is what Win98 chooses when it's not in a bad mood. Win95
chose 802.3. Who the heck knows what XP will choose? I find they all
work the same as long as they are all the same. Because Windows
changes it's default based on the position of the planets (AKA
randomly) I hard set all IPX protocols and get no failures.
3. Check to sure that something hasn't filled in a network number.
Win9x clients should be OK but some things like XP SAP fill in random
numbers for IPX. Be sure it is 0. Remove SAP if you need to. How
anyone can think it works when it assigns random network numbers is
beyond me. Reboot a couple of times and check again because whatever
changes it may change it to yet another random number. If you have
network number problems you may need to wait a half an hour or so
before your network clears it's mind enough to be able to talk
properly. I have had networks hosed for up to an hour when bad network
numbers show up.
>Or are you saying XP will tell me which protocol it's actually using?
>Wait, that's the tab where the firewall settings are made... I'm
>confused. I've had XP in the house for less than two weeks, and most of
>the first week the computer was back in the shop getting a clean
>reinstall of XP after a major hose-up.
I don't now how to figure out which it is using. I only know how to
force it to one interface then I know. Does this remind you of the
particle vs wave problem or Schrodinger's Cat?
>>>I do see quite a bit of lag accessing drives on the XP
>>>machine, but that may just be because the screen saver or other software
>>>is using up a lot of machine cycles, or other reasons -- the 100 Mbps
>>>network isn't saturated, at least.
>>
>> Cutting from two to 1 network will help a lot.
>
>Agreed, but I have to have two if the security setup I'm after is to
>work. And XP is supposed to be faster on the same hardware than
>98/98SE/Me, at least according to the MS hype. This is the same
>protocol setup that's found on each of the other machines, and there's
>no similar lag accessing one from the other.
Cutting file & print from both to one network will help a lot. I
routinely install all 3, NetBEUI for file & print, IPX for games and
JetDirect, and TCP for WAN though XP has forced me to switch to TCP
for file & print. Have as many protocols you want and you'll have no
trouble unless you have an AMD based NIC. The AMD driver cannot handle
connections through multiple protocols. If they would fix this I'd go
back to using them since they were otherwise very good.
>>>I was just about to make the switch to NetBEUI as being more secure than IPX
>>
>> Please do. If you get NetBEUI sharing files and printers I would
>> probably figure out how to switch back.
>
>First, I'll be satisfied if NetBEUI will just not crash Windows again --
>the previous crash occurred overnight after installing the NetBEUI from
>the XP CD. My wife will _not_ be happy if that repeats...
I installed it and it worked just fine... if you don't mind not
carrying file & print.
- Next message: Carlos: "IPTABLES PROBLEM"
- Previous message: Chris Severance: "Re: Packet Sniffing & Spyware"
- In reply to: The Silent Observer: "Re: Win 98SE Machine cannot see printer on home network"
- Next in thread: The Silent Observer: "Re: Win 98SE Machine cannot see printer on home network"
- Reply: The Silent Observer: "Re: Win 98SE Machine cannot see printer on home network"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
