| Title: | Welcome to Conferencing for Windows and Macintosh |
| Notice: | see note 4.16 for latest External Field Test kit information |
| Moderator: | couldb.ilo.dec.com::imslow::emchale |
| Created: | Mon Sep 19 1994 |
| Last Modified: | Tue May 20 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 185 |
| Total number of notes: | 652 |
It has been asked before but I didn't find an answer. most likely because it doesn't work directly TCP to TCP. I have a W95 PC running MS TCP. I no longer have a VMS account, my cluster STOWOA is being retired. TM Confernecing still work routing through any VMS system with UCX VMS system.But I would like to change my DECnet notesfiles addresses to TCP and access them directly, since it seems that VMS systems are in a downslope. Can it be done in TM Conferencing or the design is so DECnet centric that it's not possible? It seems to ad a double colon to any kind of addressing combinations I try in SETUP. So lets say for: [email protected] what do I enter in: node name: Conference Files name: The following doesn't work: node name:humane.lkg.dec.com Conference Files name:Internet_tools Thanks for any replies /OLD
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 182.1 | Dahhhhhh | 26031::ogodhcp-124-96-171.ogo.dec.com::Diaz | Octavio | Fri Feb 21 1997 22:14 | 10 |
I feel like a dumb-ass. I didn't change the check in the routing node. Also it needs the @ sign before the TCP address. So to answer my own question is: Node Name:@humane.lkg.dec.com Conference name:news-backbone A tout a l'heur | |||||
| 182.2 | Doesn't work | NETRIX::"[email protected]" | Bruno Eurich | Fri Mar 07 1997 14:43 | 20 |
For me, adding a "@" in front of the node name doesn't work ... e.g. for Conferencing on Galvia Using route through mode works OK, but if I disable that and use: Nodename=galvia.ilo.dec.com (which is reachable via ping) I get "Connection to galvia.ilo.dec.com failed. Network Object (Process or Socket Number) does not exist at Remote Node or Remote Node refused the connection." If I add a leading "@" to the nodename, the same happens. Other nodes behave fine configured in the above manner. A few others don't - any idea on what is wrong ? Bruno. [Posted by WWW Notes gateway] | |||||