M
Michael Grigoni
Greetings:
Win2K/SP3/TerminalServices, async demand-dial routed link to remote
LAN with NW3.12 server (link is always up). Link is PPP with IPXCP
to a Cabletron CSMIM02 terminal server (Xylogics Remote Annex).
RIP and SAP broadcasts are on the wire, and a Win9x client using
the same link (for testing, instead of the Win2K host) works properly
(NW server is browsable and one may log in).
What is needed to get RRAS on the Win2K host to dynamically use the
RIP and SAP broadcasts sent over the async wire? I've setup the
async interface to use 'standard' (as opposed to autostatic) updates
and verified that the remote gateway network is accessible using
'ipxroute.exe' but unless I manually populate the RIP table with
static routes to all networks on the remote side, the SAP table
remains empty (except for the local services).
I also added the registry value described in MSKB Q197205 in hopes
of avoiding the 'remote address is in use locally' error but I still
get the event log error described in the article even though the
local network number is now one greater than the remote network number.
Everything works properly if the routes are statically entered;
I need to avoid this as networks my change on the remote end and
the Win2K host needs to grok RIP.
I've noticed that the RIP 'Internal' interface in the RRAS 'RIP for IPX'
table is flagged as Enabled but 'down'; I have not found a way to
bring it 'up'.
All replies much appreciated.
Michael Grigoni
Cybertheque Museum
Win2K/SP3/TerminalServices, async demand-dial routed link to remote
LAN with NW3.12 server (link is always up). Link is PPP with IPXCP
to a Cabletron CSMIM02 terminal server (Xylogics Remote Annex).
RIP and SAP broadcasts are on the wire, and a Win9x client using
the same link (for testing, instead of the Win2K host) works properly
(NW server is browsable and one may log in).
What is needed to get RRAS on the Win2K host to dynamically use the
RIP and SAP broadcasts sent over the async wire? I've setup the
async interface to use 'standard' (as opposed to autostatic) updates
and verified that the remote gateway network is accessible using
'ipxroute.exe' but unless I manually populate the RIP table with
static routes to all networks on the remote side, the SAP table
remains empty (except for the local services).
I also added the registry value described in MSKB Q197205 in hopes
of avoiding the 'remote address is in use locally' error but I still
get the event log error described in the article even though the
local network number is now one greater than the remote network number.
Everything works properly if the routes are statically entered;
I need to avoid this as networks my change on the remote end and
the Win2K host needs to grok RIP.
I've noticed that the RIP 'Internal' interface in the RRAS 'RIP for IPX'
table is flagged as Enabled but 'down'; I have not found a way to
bring it 'up'.
All replies much appreciated.
Michael Grigoni
Cybertheque Museum