Forum Replies Created
-
AuthorReplies
-
I knew just after posting this we’d figure it out. Putting a call before the hcicmd command resolved the issue.
call hcicmd -p myprocess -c “mythread pstart”
Now, it doesn’t explain why it’s working on Windows Server 2008 R2 without the call but it must be a change with the shell or an OS variable that allowed the batch file to call another batch file and return to the original one.
Connor
Thank you Max!
Thanks Tim. I forgot to add that we are on CL 5.7 on Windows Server 2003. Is there a netsvc.conf file equivalent for Windows? Each time a process starts, we get a similar error to what Tim W receives.
[nci :nci :ERR /0:milallergy_cmd:02/23/2010 10:37:05] Check NetConfig error – error list: hinal1b Protocol PDL TCP/IP Host: cannot find host ‘feed.test.hinfonet.org’
The interface connects and sends transactions successfully but the errors are confusing.
I receive the error with the FQDN entered in the hosts file and also when it’s not in there.
Thanks,
Connor
Thank you for the responses! I just didn’t play around with this long enough on Friday afternoon. Today I put the FQDN in the Host field and the interface connected. As Charlie mentions, the netData.tlib file does an nslookup first therefore we don’t need the FQDN in the Hosts File.
Thanks again!
Connor
We are looking at using the FQDN to connect to foreign systems for outbound interfaces. We currently update the Host file (c:/windows/system32/drivers/etc) with the ip address and a short alias/name of the system.
123.234.567 CONNOR_TEST
We then use CONNOR_TEST in the Host field on the Protocol Properties tab.
If we switch to use the FQDN, should we enter it directly into the Host field or can we replace the ip address in the Host file with the FQDN and still use our alias/name in the Host field?
CONNOR.TEST.SYSTEM.COM CONNOR_TEST
Connor
-
AuthorReplies