| NowSMS lite / VMware / Moxa Nport 5110 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Lite Support ⬆ Archive through September 20, 2012 ⬆ |
◄ ► |
| Author | Message | |||
| Bart Timmermans New member Username: Bartsourcewarenl Post Number: 1 Registered: 05-2011 |
Hi, We use Nowsms lite in combination with DME from Excitor (Mobile Device Management tool). We have good experiences with the NowSMS lite software but at now we are facing some challenges. It's a Windows server 2008 sp1 running on VMware. On top of Windows 2008 we installed DME and all is working fine. The next step is to add SMS support to DME and we want to accomplish this with Nowsms lite in combination with a Moxa Nport 5110 Serial to IP device (because of VMware and the inability to use a local com port). This combination works perfect in a non-VMware environment in our test lab. On the VMware based server we encounter the problem that during the initial NowSMS setup wizard it seems to query the com port’s, finds the modem ok but when continuing by pressing OK, nowsms apparently finds more ports and can’t initialize them. Because of this the setup fails and won’t continue and we are stuck. Yes, we ran nowsms lite setup program with the option “runas admin”. Before replying with “we don’t support VMware” my question is simple. How can I bypass the modem quering and continue the install to finish it to later on specify manually the correct modem. I’m sure your product runs fine in this environment but it’s only the setup wizard that causes problems. Please advise ,unsupported if you will, but we don’t have a other solution. Many thanks, Bart | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3237 Registered: 08-2008 |
Hi Bart, NowSMS Lite strictly uses Windows modem APIs for querying modems. (If a modem can't be initialised, it will try to talk to the COM port directly to see if it can reset the modem, but it would only do this for the selected modem.) So I am puzzled by the behaviour that you are seeing, and I'd be curious to see more exact errors and sequence of what is displayed. After the wizard displays the modem list, when you press OK, it only tries to talk to the selected modem ... it does not query any additional modems or COM ports. Any other queries occur before the modem list is displayed. Are you able to go into the Phone & Modem Options area of the Windows Control Panel and query the modem under Diagnostics without problem? I can tell you how to manually configure the modem ... I'm just not convinced this will resolve the problem. In ProgramData\NowSMS, create SMSGW.INI with the following content: [SMSGW] Modem1=Windows modem driver name That should be enough to stop the wizard from running and allow a manual configuration. -- Des NowSMS Support | |||
| Bart Timmermans New member Username: Bartsourcewarenl Post Number: 2 Registered: 05-2011 |
Hi Des, I did go into Phone&Modems and queried the modem with succes. So that was working fine. I'll give it another go to grab the error messages. If I can't get arround it then I'll proceed with the creation of smsgw.ini. As soon as I have more info I'll post it here. Kind regards, Bart Certified DME Engineer | |||
