Could Not Initialize Communication Profile Tcp Ip Error
Contents |
(3) OnDemand (3) WebConnect 1.x and 3.x (4) Netop Portal (1) Browser-based Support Console (4) Windows Mobile & Embedded (0) Mac (1) iOS (2) Linux (1) Android (2) password validation failed due to security initialization problems on guest side Toshiba 4690 (1) SecureM2M (7) Live Guide (36) Vision Pro (819) Vision (952)
Netop Guest
Vision ME (6) Vision Mobile (1) MyVision (18) School (33) Learning Center (Vision ME and Vision PRO) (2) Additional modules and danware tools (6) Other products (6) Home » Categories » Multiple Categories Could not initialize communication profile Article Number: 104 | Last Updated: Wed, Sep 5, 2012 6:04 PM Error: "Could not open a TCP/IP socket. Address already in use. The combination of IP address and receive port is in use by another program. Please edit the communication profile, click advanced and change either." This error message indicates that another program is trying to use the same port number. This normally occurs when a computer is trying to run the Guest and Host at the same time. In the default communication configuration they both are trying to use port 6502. In most cases it is not necessary to run both simultaneously. One module should be closed before launching the other. There are two settings in the NETOP.ini file (located in C:\Windows) that address this behavior. Open this file in Notepad and look for the heading [COEXISTENCE]. Under that heading there may be the following variables: [COEXISTENCE] Coexist=1 Load_Warning=1 If these values don’t exist, they can be added and/or modified. Coexist=1 enables the auto unload and reload of the Host when launching the Guest. Coexist=2 enable the Guest and Host to run simultaneously. Load_Warning=1 will alert you when you launch a Guest that a Host currently running and it will be stopped while the Guest is running. Load_Warning=0 will disable the warning that the Host is unloading so that the Guest can run. If you need to run both the Guest and Host at the same time you would first want to configure the Guest and Host to communicate on different port number from each other. Then set the Coexist=2 and then restart the Netop Helper Service. Posted - Thu, Mar 24, 2011 8:18 PM. Filed Under: Guest, Host, Remote Control Subscribe to ArticlePrint A
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The http://kb.netop.com/article/could-not-initialize-communication-profile-104.html best answers are voted up and rise to the top Win2003 reports an error on RDP login: Could not open a TCP/IP socket up vote 0 down vote favorite We have a Win2003 sp2 server that reports the following error when you log into it via RDP-- 'Could not initialize communication profile: TCP/IP. Could not open a TCP/IP socket. Address already in use. The combination of http://serverfault.com/questions/29906/win2003-reports-an-error-on-rdp-login-could-not-open-a-tcp-ip-socket IP address and receive port is in use by another program. Please edit the communication profile, click advanced and change either.' This server is virtualized (VMWare ESXi). No errors in the logs. After logging in and closing the error, there are no other problems. Finally, what's a communications profile? windows-server-2003 terminal-server share|improve this question asked Jun 22 '09 at 18:32 smackaysmith 1131210 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote accepted Are you using the "NetOp Remote Control" product? This looks suspiciously like an error being generated by a program that it runs on startup. share|improve this answer answered Jun 22 '09 at 18:51 Evan Anderson 127k12144286 You're right. A SysAdmin finally got the auditing portion of Track-It! to 'work'. He didn't realize it was installing on servers. Thanks. –smackaysmith Jun 22 '09 at 21:30 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy p
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join http://www.tek-tips.com/viewthread.cfm?qid=67520 Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, http://www.pcreview.co.uk/threads/comunication-with-a-terminal-server.2324538/ It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework could not and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. TCP/IP Forum at Tek-Tips could not initialize HomeForumsData TransmissionCommunication ProtocolsTCP/IP Forum Could not open a TCP/IP Socket. thread581-67520 Forum Search FAQs Links MVPs Could not open a TCP/IP Socket. Could not open a TCP/IP Socket. JLO (TechnicalUser) (OP) 28 Mar 01 15:20 I have a system which gives me the following Error message after connectin to my network."Could not initialize communication profile: TCP/IP.Could not open a TCP/IP socket."I have not been able to clear this error and gain access to the internet over the LAN.The settings seem to be correct and I have quite a few other systems operating successfully using a DHCP server for IP addresses.JLO RE: Could not open a TCP/IP Socket. gunthnp (MIS) 29 Mar 01 12:20 try upgrading to winsock 2 it changes the tcp ip stack also So long and thanks for all the fish. Red Flag This Post Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames,
2006. Guest Guest We have yet registration our terminal server. After that we got following messenger every time we tried to logon to the server: Could not initialize communication profile: tcp/ip: Could not open a tcp/ip socket. Address already in use. The combination of ip address and receive port is in use by another program. Pleas edit the communication profile, click advanced and change either. Before we registration our terminal server we did not have the problem. What do I do to get ride of the problem? Guest, Jan 6, 2006 #1 Advertisements Vera Noest [MVP] Guest What do you mean with "registration"? How exactly did you do that? Can you post the EventID and Source from the EventLog on the server? Seems to me that you have duplicate IP numbers on your network. _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___ =?Utf-8?B?b2xmZXJ0?=