Page 1 of 1

Raspberry Pi 3 boot

Posted: Mon Aug 15, 2016 9:43 am
by Mn1
Hello,

When I boot raspberry pi I got following warning:

No individual configuration file found for this terminal. Parameters from all.wtc configuration file and default values of parameters will be used. On computer 192.168.2.50 run Start>WTware>Configurator, select terminal MAC B8:27:EB:98:E6:89 and create configuration file Then this message will no longer appear.



When I wrote on terminal 192.168.1.1
Then on terminal window I got:

Server 192.168.1.1 port 3389: Connection rejected. Make sure that terminal service works on this server. Try to connect using mstsc.exe.



What I have to do login?

Re: Raspberry Pi 3 boot

Posted: Wed Aug 17, 2016 12:04 pm
by aka
Hello,
When I boot raspberry pi I got following warning:
No individual configuration file found for this terminal. Parameters from all.wtc configuration file and default values of parameters will be used. On computer 192.168.2.50 run Start>WTware>Configurator, select terminal MAC B8:27:EB:98:E6:89 and create configuration file Then this message will no longer appear.
Yes, for new unconfigured terminals you should create configuration file in configurator on server. Terminal needs at least line

Code: Select all

server=...
to know where it should connect to.
When I wrote on terminal 192.168.1.1
Then on terminal window I got:
Server 192.168.1.1 port 3389: Connection rejected. Make sure that terminal service works on this server. Try to connect using mstsc.exe.
What I have to do login?
It means that your OS on 192.168.1.1 can't accept connection, there's no working terminal service on it. Connect to server Windows OS.

Re: Raspberry Pi 3 boot

Posted: Thu Aug 18, 2016 5:49 pm
by Mn1
I couldn't do any connection to Raspberry Pi 3 from terminal.

I set server parameter and connected the RPi to windows machine from ethernet.

This is my log file from network:

TCP: connecting to 192.168.1.1:3389.
[ rdpclient 585] [ 55.040149] Got EHOSTUNREACH.
[ rdpclient 585] [ 58.040106] Got EHOSTUNREACH.
[ rdpclient 585] [ 61.040093] Got EHOSTUNREACH.
[ rdpclient 585] [ 64.040103] Got EHOSTUNREACH.
[ rdpclient 585] [ 67.040093] Got EHOSTUNREACH.
[ rdpclient 585] [ 70.040094] Got EHOSTUNREACH.
[ rdpclient 585] [ 73.040103] Got EHOSTUNREACH.
[ rdpclient 585] [ 76.040096] Got EHOSTUNREACH.
[ rdpclient 585] [ 79.040098] Got EHOSTUNREACH.
[ rdpclient 585] [ 82.040091] Got EHOSTUNREACH.
[ rdpclient 585] [ 85.040123] fstream.cpp ( 437): -- ERROR -- Conection with 192.168.1.1:3389 failed, errno 113.
[ rdpclient 585] [ 85.140196] rdpclient-tcp.cpp ( 260): -- ERROR -- INTERNAL ERROR. Please, contact WTware tech support.
[ rdpclient 585] [ 85.140240] Server 192.168.1.1, port 3389: connection rejected.
Make sure that terminal service works on this server.
Try to connect using mstsc.exe.
[ pfac] [ 85.140836] Process pid 585 terminated, status 00000009.
[ gm] [ 85.150495] Final message: Server 192.168.1.1, port 3389: connection rejected.
Make sure that terminal service works on this server.
Try to connect using mstsc.exe.

[QUOTE]
Connect to server Windows OS
[/QUOTE]

How can I do it? I connected it to network via ethernet. How can I install terminal service from ethernet? I can't do tftp connection too. I am able to give more info on log files.

Re: Raspberry Pi 3 boot

Posted: Fri Aug 19, 2016 1:03 pm
by aka
What OS is running on 192.168.1.1? Can you connect to 192.168.1.1 from another windows-computer using mstsc.exe (Remote Desktop Connection)?

Re: Raspberry Pi 3 boot

Posted: Fri Aug 19, 2016 3:27 pm
by Mn1
RPi is running on 192.168.1.1 ip as I know. No I can't connect.

Re: Raspberry Pi 3 boot

Posted: Sat Aug 20, 2016 11:09 am
by aka
If RPi is running on 192.168.1.1, why are you connecting to it?
Rpi should connect to terminal server with running Windows Server OS.
Terminal said you what to do:
"On computer 192.168.2.50 run Start>WTware>Configurator, select terminal MAC B8:27:EB:98:E6:89 and create configuration file"
In configuration file you must specify at least one line:
server=...
I beleive you should specify
server=192.168.2.50
What for are you trying to connect to 192.168.1.1 if there's Rpi there?
Just create configuration file for your Pi and tell it where to connect to. It should be computer with running Server Windows OS, not RPi.