Re: Device naming using TCP/IP -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Sannan Solberg said:

> If all of users had been using named devices under Client/Access then
> this would have been quite a mess to get everyone connected back up.
> This is something to consider when deciding whether to use the named
> device function under Client Access.  Anybody had a similar problem
> yet???

This is a bad situation. We are considering switching from AnyNet and the
Netsoft router to going straight TCP/IP using device naming. We can't be
IPLing everytime we have to reset TCP/IP. Now, we haven't had to reset
TCP/IP very often. But, it would be a major pain to drop the system just to
get TCP/IP named devices back.

Mark Welte


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.