[APP] samba and inetd - telnetting into A1200

[Sanin]

Oh .. thank you !

[Sanin]

I have MKPG installer installed on the cellphone
I have Loader installed on the cellphone (yan's loader)

I've set the phone to USB modem
and I tried to open a telnet connection to the phone on windowsXP. I went to command prompt and typed telnet 172.16.16.5 and I also tried : telnet 172.16.16.6

and I always get an error saying that port 23 is closed.

Questions:
1) To Telnet do you have to set the phone on USB modem or USB storage ?
2) If I understand correctly, inetd is to start the telnet host and smbd is to shut it down .. correct?
3) I get an error saying that port 23 is closed. What do I do ?
4) How do you guys know what the IP address is (172.16.16.5-6) ?

[valkur]

here are some answers for you

1) The phone has to be in USB-Net mode. To do this, you can put it in Modem mode, and plug it into your computer. Then open Hyperterminal (Programs > Accessories > Communications), give it any name, Choose your phone in the list for Connect To and click OK, cancel the last box.

Now type "at+mode=13" with out the " and it will tell you something like "Switching to USB net mode"

Your phone is now in USB-Net mode (46p and maybe other newer ones includes the option for this in the USB mode settings)

2) Inetd is for starting and stopping telnet, smbd is for starting and stopping Samba (File sharing like your network neighborhood). When you click it once it starts, click again it stops. So if you have lost track of where it is try, click and try again.

3) Port 23 is the telnet port, its closed because either your not in USB-Net mode or inetd is not running.

4) Your computer will be 172.16.16.5 and the phone is 172.16.16.6 and thats just the way they made it.

Hope this helps.

[Sanin]

Okay,

valkur, I did everything as you mentionned...

afer I typed "at+mode=13" I get these 2 lines in hyperterminal :

"Will launch MotNet, exit modem..."

"OK"

I went back to the cellphone and clicked on inetd. It made a "beep beep" sound and then another "beep beep" sound again.

I left the first hyperterminal window open .. and I opened another hyperterminal window ... this time I selected "connect with TCP/IP"
and I punched in "172.16.16.6" port "23"
but it still says that I'm blocked on port 23....

any ideas ?

for the loader in the .system I installed yan0's loader (it appears as a smiley face in the program list on the cellphone)


I have the 44p firmware

[valkur]

After doing the first Hyperterminal and getting the "will launch MotNet..." Open a command prompt (Start > Run > cmd) In the command prompt window type telnet

The prompt will change to telnet, then type open 172.16.16.6 23

If everything is running ok, it should ask you for a username (root) and leave the password blank.

[valkur]

Sanin; You may want to start over using the first package from this thread. Also, I dont remember if that one needed the 172 address or not.

After you have put your phone into USB-net mode open the cmd prompt and type ipconfig

Look for the motorola phone and see what IP its on, if its not 172.16.16.5 then were trying to connect to the wrong address.

[Sanin]

I reinstalled the package from this thread...

After I put the phone on USB-Net mode I opened cmd prompt and typed ipconfig and this is what I got...

the ip for Belcarra USB LAN LINK #2 was
169.254.142.1 with mask address : 255.255.0.0

I'm still not able to telnet to the phone on port 23

I've read a thread somewhere that said that when you have that kind of ip .. that means that the phone assigned an ip to itself ..or something like that..

All my computers in my house are all connected through a router which is set on dhcp. Does that change anything ?

I'm stuck from this point on ...

[valkur]

ya, a 169 ip is self assigned. Try changing the IP for the adapter, Go to Network Connections in your start menu, right click on the adapter and click properties, click on TCPIP and click properties again, choose to specify an IP and type 172.16.16.5 and a subnet mask of 255.255.255.0 and leave everything else blank. In the cmd prompt window try ping 172.16.16.6

If you get a responce your ready to try telnet again, if you dont then go back to the TCP IP properties and change the IP to 192.168.1.5
If the Router in your house assigns the same range (192.168.1.XX) you could be confusing the computer, just try disconnecting it from the network while you do this.

Ping 192.168.1.2 this time and see if you get a responce.

[Sanin]

thanks valkur... I'll try that and let you know.

[admin]

?

I just telnet to 192.168.16.6 and type root thats all. didin't went tru all the process, but the main thing's the pkg files