Configuring NetBIOS over TCP/IP

How do I disable NetBIOS using netsh?
Thank you,
Alex

I had issues trying to set an XP box with WMIC command-line utility as well.  If the box is Vista or 'better' you can use WMIC to do just about anything.
Here's what I use - not much different than everyone else's suggestion:
wmic nicconfig where (IPEnabled=TRUE) call SetTcpipNetbios 1
wmic nicconfig where (IPEnabled=TRUE) call SetWINSServer "IP1","IP2"
wmic nicconfig where (IPEnabled=TRUE) call SetDNSServerSearchOrder ("IP1","IP2","IP3","IP4","IP5")
wmic nicconfig where (IPEnabled=TRUE) call FlushDNS
Obviously, I've sanitized our network settings from this.
You can search through the settings for netsh on each level with the '/?'.
Example:
c:\Scripts>netsh /?
Usage: netsh [-a AliasFile] [-c Context] [-r RemoteMachine] [-u [DomainName\]Use
rName] [-p Password | *]
             [Command | -f ScriptFile]
The following commands are available:
Commands in this context:
?              - Displays a list of commands.
add            - Adds a configuration entry to a list of entries.
advfirewall    - Changes to the `netsh advfirewall' context.
branchcache    - Changes to the `netsh branchcache' context.
bridge         - Changes to the `netsh bridge' context.
delete         - Deletes a configuration entry from a list of entries.
dhcpclient     - Changes to the `netsh dhcpclient' context.
dump           - Displays a configuration script.
exec           - Runs a script file.
firewall       - Changes to the `netsh firewall' context.
help           - Displays a list of commands.
http           - Changes to the `netsh http' context.
interface      - Changes to the `netsh interface' context.
ipsec          - Changes to the `netsh ipsec' context.
lan            - Changes to the `netsh lan' context.
nap            - Changes to the `netsh nap' context.
netio          - Changes to the `netsh netio' context.
p2p            - Changes to the `netsh p2p' context.
ras            - Changes to the `netsh ras' context.
rpc            - Changes to the `netsh rpc' context.
set            - Updates configuration settings.
show           - Displays information.
wcn            - Changes to the `netsh wcn' context.
winhttp        - Changes to the `netsh winhttp' context.
wins           - Changes to the `netsh wins' context.
winsock        - Changes to the `netsh winsock' context.
wlan           - Changes to the `netsh wlan' context.
The following sub-contexts are available:
 advfirewall branchcache bridge dhcpclient firewall http interface ipsec lan nap
 netio p2p ras rpc wcn winhttp wins winsock wlan

Similar Messages

  • Netbios over tcp/ip and over wlc-4402

    dear gentlemen,
    i have one wlc-4402 controller and some clients. how to configure the netbios over tcp/ip in the controller, so that the clients can assiciate the network.
    thank?s in advance
    michael

    Nothing, you dont have to configure anything regarding Netbios. Regards

  • Curious NetBios over TCP/IP issues and Windows SMB shares

    Hi all.
    I've got two Win 2003 R2 SP2 member servers on our AD domain. Each has shared network folders on them which are accessed by both Windows and Mac users.
    Both servers - lets call them ALPHA and BETA - are identically setup: same hardware, configuration etc. but exist on different subnets.
    Alpha has never had a problem with Mac clients connecting to any of its shares.
    Beta has, up until recently, only ever had Windows clients, but now has a couple of Snow Leopard Mac clients. When a Mac client attempts to connect via SMB or CIFS to any share on Beta - they get the prompt to authenticate and then "Connection Failed. There was an error connecting to the server Beta. Check the server name or IP address and then try again". Of course the same thing happens when I try to connect by IP.
    Curiously, the only way I can get Mac clients to connect to shares on Beta is to go into the network adapter settings on Beta, advanced, WINS and then disable NetBios over TCP/IP. Unfortunatley this breaks some unrelated stuff and I eventually have to go back in and set NetBios back to Default (enabled) and the whole thing screws up again in a few hours time again for my beloved Mac users.
    The other server Alpha never gives me any problem with Mac clients, and as I say, they are setup identically. I have been testing this with 10.6.3 clients, not sure if my 10.5 or 10.4 clients are affected.
    Can anyone offer some suggestions as to why my shares aren't accessible to my Mac clients on both servers?

    Generally it is the browser service that populates network neighborhood. This technology is no longer used with newer OS like server 2008, windows 7/8.
    Description of the Microsoft Computer Browser Service
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • How could I create a Compliance Settings that enforces NetBIOS over TCP/IP?

    Hello Everyone,
    I need to be able to enforce NetBIOS over TCP/IP on some collections. I've created a batch script  with one line that disable NetBIOS over TCP/IP but I also need to make sure this is enforced. How could I do the enforcement using Compliance Settings?
    This is the line I use to disable it;
    "wmic nicconfig where (TcpipNetbiosOptions!=Null and TcpipNetbiosOptions!=2) call SetTcpipNetbios 2"
    Thank you everyone in advance for any help

    I could probably help you with a CI for discovery and remediation, but I need (or you need to define) an additional parameter.
    If I were to run this as a powershell discovery script:
    $adapter=(gwmi win32_networkadapterconfiguration | where {$_.ipenabled -eq "1"})
    Foreach ($nic in $adapter) {
    write-host $nic.TcpIPNetBiosOptions
    what's echo'd out (in my testing) is a 0, a 1 , or a 2.
    0 means "default--use what your dhcp is offering"
    1 = enabled
    2 = disabled.
    So... from your standpoint... is a 0 or 1, (either one) acceptable?  or is only a value of 1, a hard-coded at the client (not whatever the default is from dhcp) the only acceptable value?
    fyi, the remediation script, if 1 is the only acceptable answer, would probably be this:
    $adapter=(gwmi win32_networkadapterconfiguration | where {$_.ipenabled -eq "1"})
    Foreach ($nic in $adapter) {
    $adapter.settcpipnetbios(1)
    Standardize. Simplify. Automate.

  • TMS 14.3.2 - No HTTPS Response from devices (again) - Looks like permissions issues (but possibly down to NetBIOS over TCP/IP)

    Hi All,
    Sometime ago I posted regarding an issue I was seeing on our TMS , where most of the remote devices seemingly showed up as loosing remote connection (no HTTPS Response - https://supportforums.cisco.com/discussion/12290956/tms-lost-https-communciation-devices-not-really). However, I could not figure out the root cause of the error, and now I have managed to break things again - probably due to a Java upgrade which broke TMSPE (see https://supportforums.cisco.com/discussion/12404166/looks-latest-update-java-8-update-31-will-break-tmspe-11).
    However, I thought I would look at little more closely this time to see if I could figure out the problem.
    I am seeing a lot of entries in the Security Log in TMS that seem to indicated that my the account used from a TMSPE connection has a bad or invalid password (this is set in "Administrative Tools --> Configuration --> Provisioning Extension Settings", but this password is correct (I can log into TMS with this account, and reset and restarted services etc).
    The computer attempted to validate the credentials for an account.
    Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
    Logon Account: tmspeconnect
    Source Workstation: TMS
    Error Code: 0xc0000064
    and
    An account failed to log on.
    Subject:
    Security ID: IIS APPPOOL\TMSNet40AppPool
    Account Name: TMSNet40AppPool
    Account Domain: IIS APPPOOL
    Logon ID: 0x214b6
    Logon Type: 8
    Account For Which Logon Failed:
    Security ID: NULL SID
    Account Name: tmspeconnect
    Account Domain: TMS
    Failure Information:
    Failure Reason: Unknown user name or bad password.
    Status: 0xc000006d
    Sub Status: 0xc0000064
    Process Information:
    Caller Process ID: 0x860
    Caller Process Name: C:\Windows\SysWOW64\inetsrv\w3wp.exe
    Network Information:
    Workstation Name: TMS
    Source Network Address: 127.0.0.1
    Source Port: 62114
    Detailed Authentication Information:
    Logon Process: Advapi
    Authentication Package: Negotiate
    Transited Services: -
    Package Name (NTLM only): -
    Key Length: 0
    This event is generated when a logon request fails. It is generated on the computer where access was attempted.
    The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
    The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
    The Process Information fields indicate which account and process on the system requested the logon.
    The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
    The authentication information fields provide detailed information about this specific logon request.
    - Transited services indicate which intermediate services have participated in this logon request.
    - Package name indicates which sub-protocol was used among the NTLM protocols.
    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
    I just wanted to check this like file/folder NTFS permissions, or any specific IIS permission . Is there a list of NTFS folder permissions for which the TMS required with regard to the "IIS APPPOOL", and perhaps what may need to be check in IIS?
    Oddly, the error list above refers the our "TMSPEConnect" account from the TMS domain, however this is incorrect - TMS is the machine name. Still we ARE seeing similar error which reference the actual domain name, such as:
    An account failed to log on.
    Subject:
    Security ID: IIS APPPOOL\TMSNet40AppPool
    Account Name: TMSNet40AppPool
    Account Domain: IIS APPPOOL
    Logon ID: 0x49e55
    Logon Type: 8
    Account For Which Logon Failed:
    Security ID: NULL SID
    Account Name: tmspeconnect
    Account Domain: mydomain
    Failure Information:
    Failure Reason: Unknown user name or bad password.
    Status: 0xc000006d
    Sub Status: 0xc000006a
    Process Information:
    Caller Process ID: 0xb18
    Caller Process Name: C:\Windows\SysWOW64\inetsrv\w3wp.exe
    Network Information:
    Workstation Name: TMS
    Source Network Address: 1.1.1.1 (changed external IP)
    Source Port: 47620
    Detailed Authentication Information:
    Logon Process: Advapi
    Authentication Package: Negotiate
    Transited Services: -
    Package Name (NTLM only): -
    Key Length: 0
    This event is generated when a logon request fails. It is generated on the computer where access was attempted.
    The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
    The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
    The Process Information fields indicate which account and process on the system requested the logon.
    The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
    The authentication information fields provide detailed information about this specific logon request.
    - Transited services indicate which intermediate services have participated in this logon request.
    - Package name indicates which sub-protocol was used among the NTLM protocols.
    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
    Idea welcome.
    Cheers
    Chris

    Hi all,
    After a long a fraught weekend trying to fix things, I am not that much further on, but I am beginning to understand what it isn't........ I think :(
    It looks as though the "DatabaseScanning" service, or anything that runs under the credentials of the "nt authority\network service" seems to have a problem.
    The Audit log show lot of entries where services such as"TMSWebPublic" running under the ISS Application pool "tmsnet40apppool", and actions launched under our own credential appear to communicate just fine with the device, only for the 'network service' to time out the connection a short while later. The same goes for some (not all) of the Phone book updates, which also looks as though it runs under the credentials of the 'Network Service' account.
    26/01/2015 08:30:54
    nt authority\network service
    Update
    System
    our-ctrl1
    System status
    NoResponse
    TMSDatabaseScannerService
    26/01/2015 08:30:54
    nt authority\network service
    Update
    System
    our-ctrl1
    Connection status
    NoHTTPSResponse
    TMSDatabaseScannerService
    26/01/2015 08:29:06
    tmsnet40apppool
    Update
    System
    our-ctr1l
    System status
    Idle
    TMSWebPublic
    26/01/2015 08:29:06
    tmsnet40apppool
    Update
    System
    our-ctrl1
    Connection status
    OK
    TMSWebPublic
    However, I still don't know at this point is this is related to the actual TMS front end, something to do with the domain and policies that have been applied to TMS, or the actual database, or even just communication with the back end database??? I did try running the services under a domain user (service) account, but then ran into other issues as I couldn't log into TMS.
    BTW, removing TMS, and IIS and reinstalling did fix my second issue relating to the 'Communication Errors'.
    Chris

  • Consequences of disabling NetBIOS over TCP/IP in a Windows Server 2008 environment

    Is NetBIOS required in a network with 2008 Servers and Windows 7 and Windows 8 computers? 
    There are two 2003 and one 2000 server. 
    What functionality would we loose? 
    What are the major server functions or major applications that use NetBIOS. 
    Is there any way to find if any application or server is relying on NetBIOS. 
    Any help is much appreciated. 

    Generally it is the browser service that populates network neighborhood. This technology is no longer used with newer OS like server 2008, windows 7/8.
    Description of the Microsoft Computer Browser Service
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • 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

  • 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.

  • 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

  • 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 .

  • Modbus RTU over TCP (Simex Transmitte​r and Advantech Server)

    Hey Guys,
    somehow i am not able to get a connection over TCP IP using RTU Mode (reading values) from a  transmitter which is hooked up to an advantech EKI 1542 Server. The Port is configured as an RS 485.
    i am using the modbus library and i tried to adjust the MB serial read holding registers vi to accept a TCP IP Socket input instead of an INSTR. Do you have any suggestions?
    Thanks a lot for the forum support!

    Hi Christo and welcome to NI Forums!
    Is this the ModBus library you are using? If so, I'd recomend to check out the newer, object based library available here. It has a more straightforward setup, especially for using TCP connections. You'll find an example VI for using a master, as well as a slave device, and these you'll be able to use right away without much modification. The code'll look like:
    Please test your device communication using this library.
    Kind regards:
    Andrew Valko
    NI Hungary
    Andrew Valko
    National Instruments Hungary

  • Need help with Modbus RTU over TCP communication

    Hello!
    I'm working with a project that involves communication between a LabView PC, a cRIO-9073 and a few Crouzet PLC's with XN05 modbus extentions. The issue I'm having is to get a stable and reliable connection between the units. The cRIO is communicating with the PLC's by Modbus RTU over TCP and I've created code that read and write to them in a sequential order to avoid possible ModBus conflicts. The LabView PC is sending a "ping" (boolean true) every second to the cRIO over UDP and the cRIO is then sending the "ping" to the PLC over Modbus/TCP. The PLC has a timer that waits for pings, if no ping has been recieved in 7 seconds the emergency brakes are applied and the system shuts down.
    The main problems right now is:
    * After a while I lose the connection between the LabView PC and the cRIO. "Connection with RealTime target cRIO-9073 has been lost".
     - I also get either error code 56 or 66 on the TCP link.
    * The second problem is that if I quickly pull a TP-cable from, let's say, a PLC and then directly plug it back in I want the TCP connection to quickly reestablish. However what happens is that the "pings" from the cRIO stops coming to the PLC for like 5-6 seconds (time to reestablish link?), which means the 7 second timer is almost full. One option would be to raise that timer value, but the drawback is that the system will take longer time to respond to an true error which could be bad.. My question is simply, does it really take 5-6 seconds to establish a TCP connection between a cRIO and a PLC? What affects the time? 
    I would greatly appreciate help or respons on this one. I attach a simplified version of the code I use (all variables and such has been replaced with constants). 
    Is this a good way to do a ModBus communication over TCP with 3 PLC's?  Is there a better, safer, more reliable way? All suggestions on improvment is appreciated
    Thanks!
    /J
    Attachments:
    MB_TCP.vi ‏29 KB
    MB_PLC.vi ‏28 KB

    Dear J,
    Check the state machine Architecture here.
    1. In your acquisition if you got error in any system you close all TCP connections that is not right your other systems are working fine.
    2. You go with parallel loop connection. For each PLC you run separate code with error handlers.
    3. Check the attached VI for TCP Read. Same VI you can modify and use for your ModBUS operations.
    4. In you Sub VI you are passing a constant cluster. I am not able to understand what is the use of case structure inside the subVI, In you code you are passing the constant so its always same.
    As you done previously made 3 loops or VIs to read the data in a main VI. First try to made one VI with one PLC, remove your all bugs and errors and copy it 3-time with different-different configurations.
    Thanks and Regards
    Himanshu Goyal | LabVIEW Engineer- Power System Automation
    Values that steer us ahead: Passion | Innovation | Ambition | Diligence | Teamwork
    It Only gets BETTER!!!
    Attachments:
    Tcp Host.vi ‏28 KB

  • Syslog over TCP?

    Hi all,
    Does anyone know if the MARS can accept syslog over TCP? The issue is that I want the ASA to stop making new connections in case the connection is lost to the MARS.
    Thanks in advance!
    Regards,
    Jesper

    The configuration on MARS is in the bottom of the table located at:
    http://www.cisco.com/en/US/docs/security/security_management/cs-mars/6.0/device/configuration/guide/chAsa8x.html#wp1053993
    And yes, SECURE is the key word needed, but only works if you specify TCP.
    http://www.cisco.com/en/US/docs/security/asa/asa80/command/reference/l2.html#wp1751719

  • Steps to achieve X400P7 communication over TCP/IP

    Hi Experts.
    I´m interested in information of how to set up an X400P7 scenario over TCP/IP.
    Interested in all information I can get.
    BR
    Claes

    Hi,
    The transport protocols ISDN and TCP are only used for polling channels. If a channel for incoming messages (message protocol X.400 P7 Virtual Inbound) or for incoming reports (message protocol Reports) is to be configured, the transport protocol X.400 P7 Virtual Inbound has to be used as well.
    You should  use TCP when you have  dedicated router for direct dial to mailbox.
    Regards,
    Akshay Jamgaonakr.
    Dont Forget To Reward Points .

  • Jmf -- RTP over TCP

    Not sure whether my question is logical..
    JMF transmits RTP Packets over UDP . Is there a way to configure to use TCP for media transmission instead of UDP?
    or is there any other way to use jmf for media transport between udp blocked networks.. any other way to do so.
    Please let me know.
    Edited by: alphonse.s on May 5, 2008 4:07 AM

    Hello alphonse.s
    I try to resolve this problem too. If you find any solution I will be very grateful for feedback :-)
    bye

Maybe you are looking for