mentok74
asked on
Error "Could not open a TCP/IP Socket" -Need Help Troubleshooting
I have a Win 2k3 SP1 server that keeps giving me the error below when I connect via RDP.
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. Please edit the communication profile, click advanced and change either"
I've poked around in the network properties but havent seen anything that sticks out.
Does anyone have any good information on this error or how to go about troubleshooting it?
I haven't found much on the net regarding the error message so any help would be greatly appreciated.
Thank you
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. Please edit the communication profile, click advanced and change either"
I've poked around in the network properties but havent seen anything that sticks out.
Does anyone have any good information on this error or how to go about troubleshooting it?
I haven't found much on the net regarding the error message so any help would be greatly appreciated.
Thank you
Have you tried repairing Winsock yet?
ASKER
I did run the following command
netsh winsock reset
but I still encounter the error
netsh winsock reset
but I still encounter the error
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I am connecting to a Win2K3 server via RDP from an XP SP2 client. After connecting to the server and loging in is when I get the error. The error is on the server (RDP window).
I did a netstat -an and port 3389 says Established, no errors.
I did a netstat -an and port 3389 says Established, no errors.
Established? After your connect or before? If before your connection then it may be problem. Try to use "netstat -abn" (u'll need netstat from xpsp2), it'll show you program which use 3389 port.
ASKER
Yes Established, after I connect via RDP. I did discover that if I turn off the Netop service I do not receive the error message so I think I found my conflict. Silentez, thanks for the netstat command that was one I was not aware of, pretty cool.
Thanks
Thanks