Sampsa Laine wrote: Guys, I want to create a LAT service connected to a virtual terminal port (created using TELNET/CREATE) and then when users connect to this service they get redirected over telnet to the destination. This is what I tried: lcp:==$sys$system:latcp TELNET/CREATE B4BBS 23 1 lcp create port lta1337/application lcp set port lta1337/port=tna1 lcp create service b4bbs lcp set port lta1337: /service=b4bbs However when I connect to the service b4bbs I am not redirected to the TNA1 telnet connection, but just get the normal log in screen of the host I created the service on. Where am I going wrong here? I've done some commenting on this before, but as I'm running through my backlog I figured I might as well answer this again. lcp set port lta1337: /service=b4bbs will not cause service b4bbs to connect to port lta1337:, but if you run a terminal emulation program on the VMS machine, and connect to lta1337:, you will in fact be connected to the b4bbs service. lcp set port lta1337/port=tna1 is an incomplete setup for doing a similar thing. Both are for configuring reverse lat setups. When you create a reverse lat setup, you create a local terminal (in this case lta1337:). When someone on the VMS box opens this device, they will be connected to whatever you have setup this port to talk to. There are two different ways of going about the setting up. You can: 1) Specify a specific server and port 2) Specify a LAT service Your first "attempt" specifies only the port, but not the server. Thus, if someone would have tried to connect after that had been specified, the connection would fail, since no server had been specified and thus the reverse LAT wouldn't have an idea on where to actually connect to. However, your second specification makes that void anyway, since you instead specify a service that should be connected to. In addition to all this, you also create a service called b4bbs, which is something others can connect to, and when they do, LOGINOUT will start on that port, to make it possible for the user to log in. Notice that there is no real, obvious correspondance between your lta1337: setup, and the b4bbs service, apart from the fact that if someone were to connect to lta1337:, they should be connected as with a loopback to the same machine, and presented a login session (assuming that the ethernet packets gets properly looped here, which I'm a bit unsure about). Johnny