General discussion

Locked

Identification of remote modems

By mm63 ·
Hi all,

I have a problem with a series of dialin users and need to try to document the users modem/firmware to try and discover the pattern if any.
Does anyone know how to remotely identify a modem - be it using the equivalent of AT commands etc - and without involving the end users?

Many thanks in advance,

Matt

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Identification of remote modems

by Joseph Moore In reply to Identification of remote ...

Ok, there are 3 ways I can think of to do this in a Windows environment.
The first way is if the remote systems are part of your LAN/WAN (can you PING the systems? Can you access shared folders on the remote systems?). If the systems are available to you over an Ethernet connection, then you can pull up the System Information on them.
(NOTE: this works if the clients are WinNT/2K/XP clients; I don't know if it will work against Win95/98/ME).
You could open a blank MMC window (just run MMC.EXE from the Run prompt) and then add the System Information snap-in. You then configure the snap-in to point to the Remote System, by putting in the IP address of one of your remote clients.
Then, providing you have admin-level access on the remote system, you can then choose Components -> Modem and you will see the modem info. Just what you are looking for.
And, if all of these criteria are met, the remote user won't know what you are doing.

Collapse -

Identification of remote modems

by Joseph Moore In reply to Identification of remote ...

Ok, the method #2 is to use a wardialer.
ToneLoc is the one wardialer I know of (the subject of wardialing is for another day), and I believe that ToneLoc had a remote modem identification. The way it works is it dials phone numbers, looking for modems to answer.
So, you download and install ToneLoc on your system. Then, configure it to dial the phone numbers of the modems of your remote systems. When it connects, ToneLoc reads the init commands coming from the remote modem.
If it has a match, it will tell you (again, I "think" it will do this) what kind of modem it is (as well as some other stuff that we won't get into at this time!). So, you can do it that way.
You will just have to make sure the remote systems are configured for their modems to answer an inbound call.
For more info on ToneLoc, including a download link to it, go here:
http://home.mminternet.com/~barneshouse/haq.htm

Collapse -

Identification of remote modems

by Joseph Moore In reply to Identification of remote ...

The 3rd method is not a remotely-launched inquiry. I found a tool that will identify a locally-installed modem. The tool is here:
http://members.aye.net/~bstowers/delphi/modemwiz/

So, you could send this ZIP file to your remote users, have them uncompress it, and run the EXE file. It will then attempt to identify their locally-installed modem by checking the init commands the modem accepts (it has a database of modem types).
But, this method will not satisfy your requests of identifying modems without the remote user knowing what is going on. But, now you know.


hope this all helps

Collapse -

Identification of remote modems

by mm63 In reply to Identification of remote ...

Thanks for the quick reply but not applicable.
Remote modems are V21/V22 - No dial in possibility to these modems. Has to be done from RAS or LAN side of the RAS.
Thanks anyway.

Matt

Back to Desktop Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums