HELP: pdipx and novell F/S comms

Thread View: comp.dcom.lans.novell

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Craig Goble-Garratt Fri, 04 Sep 1992 08:56

#16

Author: Craig Goble-Garratt
Date: Fri, 04 Sep 1992 08:56

62 lines
2459 bytes

Hi!

Could anyone HELP with the following problem:


My setup:

	a 386-DX (25 MHz)
	NI5210 8 bit NIC
	DOS 4.01
	Windows 3.1
	X-vision 4.0

	I load the NI5210 packet driver with the -n & -w options
	I load ipxbyu.com

My problem:

	My environment is very unstable. My machine tends
	to hang, when working from within windows, while
	running X-vision and/or MS-mail for windows.

My attempted solution:

	I down loaded intelpd.zip and replaced ipxbyu.com
	with pdipx.com.

What happened next:

	When I loaded netx.com a received the response 
	"File Server not found". I received this response
	when trying to connect to a File Server (F/S) 
	running 2.2 as well as a F/S running 3.11.

	I then cpatured the packets on the network using 
	'SNIFFER' and found that the packets sent by my 
	PC were standard "Netware Nearest Service Query"
	packets and when I tried to connect to the 2.2 F/S
	the server responded with a standard response but
	my PC did not pick up this response. When I tried
	to connect to the 3.11 server the server did not 
	respond at all.

NOTE:	I even tried re-generating the pdipx.com file
	by using 'nlink.exe', the supplied sipx.obj and
	the ipx.obj supplied with windows 3.1 but I 
	experienced the same response as described above.

Our F/S speak 802.3 and when using the econfig.exe program
to check what the pdipx.com was speaking it returned 802.3.


CAN ANYONE OUT THERE ADVISE ME ON WHAT I MIGHT BE DOING WRONG 
OR WHAT I CAN DO TO FIX THIS PROBLEM. PLEASE E-MAIL ME WITH 
YOUR SUGGESTIONS. I WILL ALSO WATCH THIS GROUP FOR POSTINGS.

Tx :-)
__@__@__@__@__@__@__@__@__@__@__@__@__@__@__@__@__@__@__@__@__@__@__@__@__@__@__
Craig G. Goble-Garratt                          +27-12-841-4715 (phone)
CSIR Information Services                       +27-12-841-4109 (fax)
Pretoria                                        cggarrat@dobs.csir.co.za
################################################################################

Re: HELP: pdipx and novell F/S comms

#14

Author: johnny
Date: Tue, 08 Sep 1992 10:13

37 lines
2116 bytes

In article <cggarrat.12.0@csir.co.za> cggarrat@csir.co.za (Craig Goble-Garratt) writes:

I wrote:

>	I load the NI5210 packet driver with the -n & -w options
>	I load pdipx.com
>
>	When I loaded netx.com a received the response 
>	"File Server not found". I received this response
>	when trying to connect to a File Server (F/S) 
>	running 2.2 as well as a F/S running 3.11.
>
>NOTE:	I even tried re-generating the pdipx.com file
>	by using 'nlink.exe', the supplied sipx.obj and
>	the ipx.obj supplied with windows 3.1 but I 
>	experienced the same response as described above.
>
>CAN ANYONE OUT THERE ADVISE ME ON WHAT I MIGHT BE DOING WRONG 
>OR WHAT I CAN DO TO FIX THIS PROBLEM. PLEASE E-MAIL ME WITH 
>YOUR SUGGESTIONS. I WILL ALSO WATCH THIS GROUP FOR POSTINGS.
>

A number of people responded and suggested that I should rather use the TSR
WINPKT.COM, rather than the -w option on the packet driver. Thanks for the 
advice but... I had already tried this without any luck. However, someone 
did mention that pdipx.com does not need the packet driver to load with the 
-n option because it does the necessary conversion itself. THANKS!!! This 
was the reason why I could not get pdipx.com to work.

Yet another however, I did mention (see NOTE above) that I tried to 
regenerate the pdipx.com file to see if this would work....it does not! I 
get no response from the F/S and this is consistent whether or not I load 
the packet driver with the -n option. An unfortunate side-effect of this is 
that, if the F/S is running 3.11, then it hangs solid!!!
ANY IDEAS?

Once again, thanks to all those who offered advice. :-)

Re: HELP: pdipx and novell F/S comms

#17

Author: Alan Strassberg
Date: Wed, 09 Sep 1992 19:00

22 lines
1375 bytes

In article <johnny.13.0@csir.co.za> johnny@csir.co.za writes:

>Yet another however, I did mention (see NOTE above) that I tried to 
>regenerate the pdipx.com file to see if this would work....it does not! I 
>get no response from the F/S and this is consistent whether or not I load 
>the packet driver with the -n option. An unfortunate side-effect of this is 
>that, if the F/S is running 3.11, then it hangs solid!!!
>ANY IDEAS?

	When you regenerated pdipx you probably reset it's packet
	type. Check this with:

		ECONFIG pdipx.com

	It will report back 802.3 or 8137 packet type. To set it
	to what you want (obviously the opposite of what it says)

		ECONFIG pdipx.com shell:e 8137

					alan
----
Alan Strassberg		oetl1.scf.lmsc.lockheed.com	(408) 425-6139

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