Solution to PathWorks hanging server's DECnet... Thanks

Thread View: comp.sys.dec.micro

3 messages

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

3 total messages Started by mcginnis Tue, 28 May 1991 13:05

#1079

Author: mcginnis
Date: Tue, 28 May 1991 13:05

10 lines
951 bytes

Thank you for your replies to my posting about my PathWorks for DOS
client killing DECnet on our server (VAX).  The NETSETUP utility 
that configures the client PC requests only one DECnet node name
and address; that for the "file server".  I don't know why it didn't
seem strange to me that it never asked for the client or PC node
name and address.  NETSETUP gave the client the DECnet node name 
and address of the server and when the client started up DECnet
the servers DECnet would choke.

Thanks again.

OK, so here's another Pathworks problem...

#1080

Author: System Janitor
Date: Tue, 28 May 1991 15:52

10 lines
796 bytes

The folks that wrote the tcp-ip transport part of pathworks must be working
straight from the RFCs or something (I never thought I'd complain about 
that!).

I believe Pathworks is hardcoded (non-configurable) to broadcast on ones.

What about us folks who have big old networks all set up where everyone
broadcasts on zeros?

-Mike

Re: OK, so here's another Pathworks problem...

#1081

Author: Marcus J. Ranum
Date: Tue, 28 May 1991 16:46

9 lines
858 bytes

hubcap@hubcap.clemson.edu (System Janitor) writes:

>I believe Pathworks is hardcoded (non-configurable) to broadcast on ones.

	The folks who work on Pathworks are aware of the problem - I don't
know when/what fix may be forthcoming, though. You should explain the
importance of the issue to your sales rep.

mjr.

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