Connecting to labview over TCP/IP port

I have got an undocumented project to maintain, it has a Java UI code, which connects with some component of LABVIEW over
TCP/IP Port = 1234
and over this port it sends commands for clear, get, set
I need links for understanding the component from LABVIEW which is been accessed over port 1234
I have installed LABVIEW Run time 2013, and do not know which PROCESS the Java code is trying to connect over TCP/IP, and I do not see any of the RT processes binding to port 1234.
Any pointers/links would certainly help me!
Thanks,
-Vikrant

Can you define what you mean by "component of LabVIEW"?
The LabVIEW runtime engine is just a required component to run any custom build LabVIEW executable or dll. So, what is it?
You also mention RT processes. Does this run on an RT system? What is running where? If you are connecting to a remove LabVIEW RT system that runs a service on port 1234, you don't need LabVIEW or a run time engine at all on the local side.
At this time we don't have any useful information from you. Please be significantly more detailed! Thanks.
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

Connecting to non-secure listener port over TCPS

Hi,
I am trying to connect to non-SSL port over TCPS.
When I use tnsping, it hangs.
When I do an OCIServerAttach, it hangs.
Client is 10.2
And Database server is 9.2 and higher..
Any way I can find out why this is happening??
-Harsha

Maybe I'm not getting the point, but when you do not use SSL on this port, why do you want to use TCPS. Wouldn't TPC be a better choice?
cu
Andreas

How to send joystick data over TCP connection

Hi all,
I am a long time Labview discussion forum user for learning, but this is my first time posting a question, I hope somebody can help me!
In the attached VI I am trying to send data from a joystick over a TCP connection. I can send data fine using the TCP examples (in fact the majority of my VI is just a copy of the example). However I am to the point where I do not know how to send all the data necessary (3 axis data, 12 buttons, and the POV data) over TCP. Strings, clusters, and arrays were never my strong suite and converting between them is a nightmare for me.
Basically I am trying to send each axis data (X,Y, and Z), button data (12 buttons), and POV data (the POV data will be calculated to adjust the position of a camera, so the immediate data is not important, I will add functions to add the change in the button movements to write a standing position for two servos [pan and tilt], for which that I will need to send over the TCP connection) over the TCP connection to control various cameras and motors. I don't know if it is posible to send that much data over a TCP connection in one write VI through a string, and also how to separate the string on the other side in order to control the client VI.
Again, the actual TCP communication I get, and can operate fine, just formatting all the data into a string (or whatever is required) so that I can unpack on the other side is the issue here.
Another question I have (not impotant to get the program running just might make it easier on me) is can a TCP server (which sends the data to the client) also recieve data back from the client on the same port ( for example sensor data and digital positions [on,off])? Or do I need to set up two TCP communication loops with the first client acting as the server on a different port than the first, which then sends the data to the original server, which also has a client TCP configuration in another loop? I hope this makes sense...
One final question.....I already have a solution to this but using labview for the entirety of this project would be nice. I use skype to stream 1080p video from a webcam to my computer so I can view live feed. Can labview do this? This would be awesome if so, I am just not sure if the communication protocols in use could support real time (or as close as possible to streaming) for 1080p video.
Thanks all in advance for your help,
Physicsnole
Attachments:
cameraserver.vi ‏24 KB
cameraclient.vi ‏18 KB

Physicsnole wrote:
In the attached VI I am trying to send data from a joystick over a TCP connection. I can send data fine using the TCP examples (in fact the majority of my VI is just a copy of the example). However I am to the point where I do not know how to send all the data necessary (3 axis data, 12 buttons, and the POV data) over TCP. Strings, clusters, and arrays were never my strong suite and converting between them is a nightmare for me.
Well, you cast the axis info cluster to a string, but then you cast it back to an array of DBL. Thatr's not compatible. You should probably cast it back to an "axis info" cluster of exactly the same type. Go the the other VI and right-click the cluster wire to create a constant. Now move that diagram cluster constant to the other VI and use it as type.
Your default ports don't seem to match. You seem to have client and server roles confused. In the sever you create a listener, but then you start sending packets, even though no connection is established. The connection needs to be initiated by the client.
Your client stops the loop the first time a timeout is encountered. Shouldn't that be more permanent? Also, please retain code clarity and avoid unecessary complexities. For example, replace the "not or" with a plain "or" and change the loop to "stop if true"
Physicsnole wrote:
Basically I am trying to send each axis data (X,Y, and Z), button data (12 buttons), and POV data (the POV data will be calculated to adjust the position of a camera, so the immediate data is not important, I will add functions to add the change in the button movements to write a standing position for two servos [pan and tilt], for which that I will need to send over the TCP connection) over the TCP connection to control various cameras and motors. I don't know if it is posible to send that much data over a TCP connection in one write VI through a string, and also how to separate the string on the other side in order to control the client VI.
You can send as much as you want. The casting to/from string is the same as described above.
Physicsnole wrote:
Another question I have (not impotant to get the program running just might make it easier on me) is can a TCP server (which sends the data to the client) also recieve data back from the client on the same port ( for example sensor data and digital positions [on,off])? Or do I need to set up two TCP communication loops with the first client acting as the server on a different port than the first, which then sends the data to the original server, which also has a client TCP configuration in another loop? I hope this makes sense..
The primary function of a "server" is to wait for a connection and then communicate with the client once a conenction is established. An established TCP/IP connection is fully two-way and both sides can send and receive.
LabVIEW Champion . Do more with less code and in less time .

HP/Agilent Infiniium 54831B scope - how to connect with LabView 6.0 by LAN (TCP/IP)

Dear,
I'm looking inf. how to connect Agilent Infiniium 54831B scope with LabView 6.0 by LAN (TCP/IP).
Thanks in advance.
Regards,
Z.Mrowka
mailto:[email protected]

Hello,
If the instrument is capable of being controlled from its TCP/IP port, it will be possible to communicate with the instrument from LabVIEW using VISA.
The VISA resource name input will need to be entered manually and is a little different from the normal Serial or GPIB format. The format is as follows:
For SOCKET connections, this is just like the traditional TCP functionality in LabVIEW. An example string that connects with the NI FTP site is:
"TCPIP::ftp.ni.com::21:OCKET"
For INSTR connection, this requires a device that supports the T&M standard LAN instrument protocol. An example of this (that we have tested with) is the Tektronix 3054 Scope. A string that connects with this scope is: "TCPIP::HostnameOrIP::gpib0,1::INSTR"
I hope this
helps,
Anthony Bacak
National Instruments
Applications Engineering

SSL Connection over TCP using SSLSocketFactory to remote C++ Server

Hi.
Despite my traversing through the archives, I could not find a
solution to my problem. So hopefully, that would mean i have a simple
isolated, and FIXABLE problem :-)
My web application running under Weblogic 7.01 as a servlet needs to
connect to a remote server using SSL over tcp.
The server is a C++ app using openssl libraries to serve up a
self-signed certificate.
The code fragments to do so look like this:
     SSLSocketFactory sf =
(SSLSocketFactory)SSLSocketFactory.getDefault();
     connection = sf.createSocket(host, port);
     output.write(...)
     output.flush();
Upon the flush, I get the following error:
java.io.IOException: Write Channel Closed, possible SSL handshaking or
trust failure
     at com.certicom.tls.record.WriteHandler.write(Unknown Source)
     at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown
Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown
Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown
Source)
     at com.certicom.tls.record.ReadHandler.interpretContent(Unknown
Source)
     at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown
Source)
     at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown
Source)
     at com.certicom.tls.record.WriteHandler.write(Unknown Source)
     at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:67)
     at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:125)
     at java.io.DataOutputStream.flush(DataOutputStream.java:99)
My guess is that its complaining about not trusting the certificate
being sent back by the server.
I typically use JSSE for this application when running within other
appservers, and
this application has no problems. But because i've run into issues
with using JSSE in WL7.01 (another topic
for another day), I'm using the default WL ssl library.
I have set weblogic.security.SSL.trustedCAKeyStore=d:\bea\weblogic700\server\lib\cacerts,
and imported my
certificate into that cacerts file. This doesn't seem to fix my
problem. Is there another truststore
that my webapp may rely on? Where within the admin console can I
figure this out?
Or am I on the wrong track here?
Also, if its any clue, elsewhere within the same application, I make
https requests to another
web app running under the same weblogic server - and that is fine - I
use the URLConnection class in those cases.
Any help is much appreciated!
Thanks
Ed

Hi,
Can you show us the stacktrace?
/Kaj

Pls confirm SMB over TCP/IP w/o NetBIOS (port 445)

Pls confirm that Mac OS X natively supports SMB over TCP/IP w/o NetBIOS layer, i.e. have you been able to connect to a Windows mashine on port 445 (not 139) w/o port remapping.
MB 2.0 Mac OS X (10.4.9)

I just talked for 30 min with one of the university network sysadmins. Apparently, OS X does NOT support "native" SMB over TCP/IP on 445 (i.e. w/o handshake session on 139). It probably could be done thru VPN or DAVE software, but not thru Finder. There doesn't seem to be an easy fix to smb.conf or nsmb.conf that might do that.
Most of the firewalls around here filter 139 (but not 445) so PC can share with PC over Samba, but Mac can not. Way to go, Apple.

How to read data over tcp/ip using labview

Hi,
I have a network enabled force transducer (6-axis load cell). I know its IP addr. and the data format it is sending the data out (7 32-bit DWORD, One status and 6 axis force data) . I have been playing around with the simple data client.vi example program.
When I executed the program using the devices IP addr. I used to get error 63: TCP/IP connection open. Then I ran the program using localhost in IP addr field, the program executes now indefinetly at one block only. I am attaching the screenshot for ref.
Thanks.
Sasi.
Attachments:
TCP-IP.JPG ‏62 KB

Hello,
I'm wondering if you can create a rather simple VI that just tries to open and close a TCP connecting to your transducer. All you would need is a TCP Open and a TCP Close wired together with the proper IP address etc. Does this run? I did look to see if there was any NetFT information and I could not find anything. I feel that the problem lies in the communication protocol between your transducer. Another place to see if you can connect to it would be to try hyperterminal. You can access this in Windows XP by clicking Start»All Programs»Accessories»Communications»HypeTermina. Using this, you can try and connect to your instrument with TCP/IP outside of LabVIEW. You might also want to get in contact with the manufacturer to verify that third-party software can indeed communicate with it. There may be a specific set of instructions that need to be sent to the transducer in order to initiate the connection and then read from it. These may be in the form of serial commands that would need to be sent over TCP. What is the make and model of your transducer?
-Zach
Certified LabVIEW Developer

Sql server 2012 express - tcp/ip connection to named instance using dynamic port not working

I have a named instance on a SQL 2012 Express server that won't connect via TCP/IP when wanting to connect off of the dynamic port. I can connect via shared memory locally on the server.   I can connect to the namespace when specifying the
dynamic port listed in the configuration manager.
This is the only named instance on the server and it is not the default.
TCP/IP is enabled
Allow Remote connections is enabled
the server browser service is running
I can connect via the dynamic port number
I am testing the connection locally on the server, so I don't believe a firewall is the issue. I get the same results if I test it from a remote computer.
When using the sqlcmd (sqlcmd -S tcp:SQLSRVR\NAMEINST -E) I get the message that "the requested protocol isn't supported [xfffffffff]".   The command (sqlcmd -S tcp:SQLSRVR\NAMEINST,59992 -E) works.
Through SSMS, I get the message "the connection was actively refused".
On other boxes, I can connect with the named instance without having to specify the port.
I have looked through the sql logs and nothing much shows up. The log does show that is listening on the port # for ipv4 and ipv6.   There is also a line in there talking about the SPN not being registered and not to worry about it if
you are not using Kerberos. I logged in through shared memory and it said I was using NTLM.
Any help would be appreciated.
thanks.

Hi clw,
I’m writing to follow up with you on this post. According to your description, I do a test, if you configure the database engine to listen on a specific TCP port (59992), and
the port is opened in the firewall. If you want to connect to the SQL Server instance, you 'd better to
use the port number.
In my opinion, by default, the default instance of the Database Engine uses port 1433, usually, if you have configured the server to listen on a non-default port number, when an instance of SQL Server uses dynamic port allocation, the connection string that
is built at the SQL Server client does not specify the destination TCP/IP port unless the user or the programmer explicitly specifies the port. Therefore, the SQL Server client library queries the server on UDP port 1434 to collect the information about the
destination instance of SQL Server.
If UDP port 1434 is disabled, the SQL Server client cannot dynamically determine the port of the named instance of SQL Server. Therefore, the SQL Server client may be unable to connect to the named instance of SQL Server. In this situation, the SQL Server
client must specify the dynamically allocated port where the named instance of SQL Server is listening.
For more information about configuring an instance of SQL Server to listen on a specific TCP port or dynamic port, you can review the following article.
https://support.transfrm.com/entries/503111-How-to-configure-an-instance-of-SQL-Server-to-listen-on-a-specific-TCP-port-or-dynamic-port
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

Unable to connect to database; verify that database TCP/IP port service is

Hi i have a problem with a few servers when i'm trying to upgrade from SAP 2007 SP00 PL47 to SAP 2007 SP1 PL06, i run the upgrade for SBO-COMMON and gives me the message Unable to connect to database; verify that database TCP/IP port service is started, and i don't know why, i hope you can help me.
Julieta

Hi,
Ensure that the connection to the database is configured properly.
1. Check that the TCP/IP port is not being blocked by a Firewall.
2. Set the Server's Remote Connection to accept TCP/IP connections.
Microsoft SQL Server 2005 -> Configuration Tools -> SQL Server Surface Area Configuration -> Server Surface Area Configuration for Services and Connections -> MSSQLSERVER -> Database Engine -> Remote Connections
Restart the 'SQL Server (MSSQLSERVER)', and run the upgrade again.
Hope this will resolve your issue !

Computer unable to connect to servers over certain ports through AEBS

Despite being a die hard windows user, I love my AEBS. Unfortunately, I have recently experienced an issue which has forced me back to my old LinkSys router.
With my computer which runs Windows Vista, when I try and connect to Age of Conan (a game which requires communication over port 7025) the computer is unable to establish a connection through the AEBS and the game hangs. However, the game also requires a connection on a variety of other ports (e.g. 7000) and these ports connect just fine.
- What is most frustrating is that this /used/ to work - I played the game regularly before going on hiatus for a couple of months and just recently came back.
- When I connected previously, it was before the firmware upgrade to 7.3.2. This is just anecdotal, as I'm not sure this is the cause. I've tried backing out to 7.3.1 and 7.2.1 but neither worked.
- I've tried creating a port mapping rule which will route all 7025 traffic to my static IP, no dice
- My wife's computer which runs XP64 is able to connect just fine
The only thing I can think of is a possible relation to IPv6 which Vista supports but XP doesn't. IPv6 has always been set to link-local only. Is there any way to completely disable it?
Any suggestions are welcome. Thanks.

Yes you are right once the router is configured then you can use the desktop wirelessly , if you have the wireless adapter on the desktop .. However before that you need to connect your computer with the router with a ethernet cable and configure the router first and that can be done by using the CD or manully as well.

When i plug the USB for my iPad into my computer it will connect then disconnect over and over again untill i wiggle the usb around alot. This is happening to all my ports. But not on the other computer.

Hi. Whenever i plug my iPad (Happens with ipod and iphone too) to my computer usb for itunes is will connect, then disconnect over and over again. It has happened for a long time but doesnt happen on my other computer. how do i fix this?

If you have a spare cable, try using that. But the fact that this doesn't happen on your other computer (I assume using the same old cable) leads me to conclude that something else is at work. Maybe even the "bad" computer.

Help with connecting to NIST NTP server on port 123

I can get NIST time in Daytime format using the rt_nist_date_time.llb example posted on ni.com, but I cannot connect to NIST NTP format time data using port 123. I freely admit to being over my head with this stuff, and have spent much of this Thanksgiving holiday reading about UDP and TCP.
The attached vi summarizes what I've tried so far. The UDP case is what I thought would work, but I can't come up with a network address that the UDP-open vi likes. Can anyone out there help this n00b tell the time?
The attached file is supposed to be in 8.0 format, although I'm working in 9.0
Here is a link discussing the time formats: http://tf.nist.gov/service/its.htm
Jeff
Solved!
Go to Solution.
Attachments:
UDP.vi ‏17 KB

jstevens wrote:
THANK YOU!!! I don't think I ever would have come up with connecting the web address to a Read or Write UDP rather than the Open UDP block. Not to mention starting by opening port zero.
Unlike TCP, UDP is a connectionless protocol. Here's a quick explanation in different words.
A udp packet travels from a [sourceIP, sourcePort] to a [DestinationIP, destinationPort].
UDP open basically reserves a local port used for sending (soucePort) and receiving (incoming packet with that same destinationPort). Since some local ports are always in use, you would generate an error if you would accidentally pick a used port. Picking zero is useful for requests (as in this case!), because the OS will pick an unused ephemeral port. The actual source port number does not matter because the NTP server will just send the reply packet back to whatever port it came from. (If you would write your own NTP server in LabVIEW, you would of course need to set the local port to 123, and would get a conflict if another NTP server is already running on your rig). Writing an NTP server in LabVIEW would be a trivial modification to the current code, try it! . Simply listen for packets on port 123, form a response packet based on the timestamp, and send it to whatever IP/Port it came from (that info is available from udp read) and then go back to listen for new requests.).
UDP write sends a packet to the server using the above opened local port as source port. You can use the same connectionID to write to several other servers and ports, because UDP is connectionless. (TCP is connection based, so a TCP connection involves a defined source/destination pair)
UDP read listens for incoming packets from all over the world at that same local port. It is very unlikely, but theoretically possible that other UDP packets will arrive at that same port, so you could even filter to make sure to read incoming packets until they match the port and IP of the original request. The current code is somewhat vulnerable to a DOS (denial of service) attack for example as follows: Imagine the guy in the next cubicle had means of sniffing your network traffic. He could write a small program that looks for your NTP requests and then immediately starts flooding your IP with meaningless UDP packets to the sourcePort you just used. The current program only reads one packet and thus will never see the return packet from the NTP server.
UDP close frees up the local port and the computer is now no longer listening for packets on that port. Of course you could keep the port open for the duration of the program, especially if you intend to send UDP request once in a while during execution.
Makes sense?
LabVIEW Champion . Do more with less code and in less time .

Establish connection between labview and Lantronix XPort Pro

Hi:
I am pretty new in this field. I just got into grad program, and I have been asked to establish a TCP/IP connection between Lantronix XPort Pro and labview 8.5. The goal is to get data from the server (Lantronix XPort Pro) and put them into labview and modify them, then I need to send modified data back into server.
The server has registered into local network wirelessly, it has IP 192.168.5.117 in port 26.
I would really appreciate your help and comments.
cheers!
Kian.

Which field are you "new" to? Programming in general? Programming in LabVIEW? TCP/IP?
Have you taken a look at the TCP/IP examples that ship with LabVIEW? There are simple Data Client/Data Server examples that show transfer of data over TCP/IP. You will likely need to do something very similar. Does the XPort Pro have a TCP/IP listener running? Do you have a communication protocol defined?
Also, if you are new the LabVIEW, have you gone through any of the tutorials? To learn more about LabVIEW it is recommended that you go through the introduction material, tutorial(s), and other material in the NI Developer Zone's Learning Center which provides links to other materials and other tutorials. You can also take the online courses for free.

Multi Thread Server over TCP/IP

Multi Thread Server over TCP/IP. Does it work?
In my box it works only over IPC protocol.
null

S C Maturi (guest) wrote:
: Mark Malakanov (guest) wrote:
: : Multi Thread Server over TCP/IP. Does it work?
: : In my box it works only over IPC protocol.
: Mark,
: Multi threaded server over TCP/IP will not work with
: the current distribution of Oracle 8.0.5 on Linux.
: This is corrected and a patch would be released soon.
: Maturi
tcp 0 0 bock.nettek-ll:listener bock.nettek-
llc.co:4196 ESTABLISHED
tcp 0 0 bock.nettek-llc.co:4196 bock.nettek-
ll:listener ESTABLISHED
(I have serveral of these)
TNS Ping Utility for Linux: Version 8.0.5.0.0 - Production on 07-
JAN-99 18:45:52
(c) Copyright 1997 Oracle Corporation. All rights reserved.
Attempting to contact (ADDRESS=(PROTOCOL=TCP)(HOST=localhost)
(PORT=1521))
OK (440 msec)
...and from my install log you see that I selected MTS:
-[ YESNO
Q> Would you like MTS (Multi-Threaded Server) configured
and the SQL*Net$
A> TRUE
Please explain? Will TCP/IP MTS work via the loopback adapter
only? So far I have not tried a remote TCP/IP connection.
-STEVEl
null

Safety of MS Sharing on LAN over TCP/IP via NetBIOS and/or Direct SMB

Shalini Sampath Kumar at http://answers.microsoft.com/en-us/windows/forum/windows_7-security/ suggested I post this question over
here:
What is the safest recommended way to set up MS File and Printer Sharing on a LAN with both Windows 7 Pro and XP Pro machines? Does "Direct hosting of SMB over TCP/IP," help? What about setting a "Scope ID" (or did that go out
with Windows NT)?
Background: I've been trained to be paranoid about NetBIOS over TCP/IP. Right now I have only XP Pro machines on my peer-to-peer workgroup LAN (behind a NAT router and with Simple File Sharing turned off), on which File and Printer Sharing has been
unbound from TCP/IP and bound to NetBEUI instead, so I feel fairly safe. Port scanning by ShieldsUp doesn't see any ports through the router, open or closed -- in other words, it appears to be "stealthed," for what that's worth. With
NetBIOS disabled on all computers inside the LAN, however, can I perform a valid test of what will happen when File and Printer Sharing is re-bound to TCP/IP?
My New Problem: I'm planning to add Window 7 Pro machines, for which NetBEUI isn't an option, and then to transition entirely to Win7 before XP goes off extended support in April. I will still use a peer-to-peer architecture with password-protected
sharing turned on (no HomeGroup). It appears that I can still get rid of NetBIOS (and WINS) in favor of "Direct hosting of SMB over TCP/IP," which sounds safer. Apparently then only port 445 will be vulnerable instead of ports 137-139.
In any case I want to do everything I can to protect my file-sharing port(s) from the Internet (e.g., from anyone who might break into my LAN either by making a wireless connection or by hacking the router itself). Can anybody give a clear set of steps
to change sharing from NetBIOS (which I would like to disable entirely) to direct hosting of SMB and to verify that I'm protected as well as possible?
I will have to completely revamp the network-file-sharing configuration of my XP machines as soon as the first Win7 machine goes on line (and possibly tweak the configuration of Win7 as well), perhaps as early as this week. I want to do this in the way that
maximizes security to the extent possible. Thanks in advance more details and guidance on this topic! -- JCW2
P.S. -- These computers are all laptops and will be used away from my home LAN -- another reason for paranoia about File and Printer Sharing. I realize that Windows 7 provides an easy way to disable F&PS by selecting any new network location as
"public," but XP does not (as far as I know). Fixing that will take more effort and be harder to remember... -- JCW2

Removing the NetBIOS transport has several advantages compared to NetBIOS over TCP, you can find detailed infromation in the following KB
Direct hosting of SMB over TCP/IP
http://support.microsoft.com/kb/204279/en-us
Yolanda
TechNet Community Support
Hi again -- I think I'm slowly catching up with you. Following from my previous message...
Somebody on another forum mentioned creating "Hosts" files on each computer to substitute for the DNS server that I don't have on my workgroup. This is intriguing if I can figure out how to set it up. (I've heard it said that taking control of
your "Hosts" file is a good safety precaution anyhow, since it is a frequent target of hackers trying to divert legitimate Web requests to their own malicious sites.) Does anybody have tips and/or references that would help me accomplish the name resolution
there?
Finally, what functionality do I really lose by going the Direct-Hosting-of-SMB-with-Hosts-file (or drive mapping) route as opposed to using NetBIOS over TCP/IP? Granted, any new machine added to the network would also have to be added to all the "Hosts"
files (or mapped to a new drive letter) on each machine; but given that I already have to add it to the MAC filter and assign it a DHCP reservation in my router, this isn't a heavy burden for something that doesn't happen often. Would everything then
work the same as if NetBIOS were providing the name resolution?
One missing piece that I see so far -- it's not obvious how this same trick would apply to printer sharing (although I'm not using that feature right now anyhow). Could this be handled seamlessly through the "Hosts" file as well?
Thanks and Best Regards to All -- JCW2

Connecting to labview over TCP/IP port

Similar Messages

Maybe you are looking for