jstewart@sce.carleton.ca (John Stewart) (10/26/89)
We recently started using class C subnetting on our class B network. One problem we ran into was that our 3Com/Bridge CS/100 terminal servers were unable to connect to machines on another subnet. I managed to fix that problem by adding the routed port number to the list of "listener" port numbers so the Bridge boxes would look at RIP packets. Now the problem has returned. Only the 3Com/Bridge CS/100 boxes seem to be affected, everyone else on our subnet (mostly Sun's) has the "right" routing information to reach machines on other subnets. I've checked the configuration and the boxes should still be picking up RIP information. Does anyone have any idea of how to fix this problem? -- Support the President's War On Long Usenet Signatures Committee