Synergy 1.3.7: server refused client with our name
I'm trying to connect a Windows 7 server and an Ubuntu 11.04 client with Synergy 1.3.7.
I have checked that the server is listening on the correct port by running netstat -ano
. I have also checked that the client can connect to the server on this port with telnet.
The server has the screen name Rupert-PC.
The server is setup with both the server screen, Rupert-PC, and the client screen, Ubuntu.
I have checked that the client is called ubuntu by running hostname
. I have also tried specifying it directly by called synergyc -f --name ubuntu 000.000.000.0
.
However, the client still can't connect and gives the following error:
Error server refused client with name "ubuntu"
Any ideas on what else I can check to get this working?
Edit: I've also tried using Synergy 1.4.3 beta but got the same result.
windows-7 synergy ubuntu-11.04
add a comment |
I'm trying to connect a Windows 7 server and an Ubuntu 11.04 client with Synergy 1.3.7.
I have checked that the server is listening on the correct port by running netstat -ano
. I have also checked that the client can connect to the server on this port with telnet.
The server has the screen name Rupert-PC.
The server is setup with both the server screen, Rupert-PC, and the client screen, Ubuntu.
I have checked that the client is called ubuntu by running hostname
. I have also tried specifying it directly by called synergyc -f --name ubuntu 000.000.000.0
.
However, the client still can't connect and gives the following error:
Error server refused client with name "ubuntu"
Any ideas on what else I can check to get this working?
Edit: I've also tried using Synergy 1.4.3 beta but got the same result.
windows-7 synergy ubuntu-11.04
1
The solution was simple: I changed the server screen name from Rupert-PC to rupert. I'm not sure why this worked. Maybe it didn't like the capital letters or the hyphen. Unfortunately I can't add this as an answer for another 8 hours as my reputation is below 100. I'll to remember to do so then.
– Rupert Madden-Abbott
Aug 9 '11 at 0:29
add a comment |
I'm trying to connect a Windows 7 server and an Ubuntu 11.04 client with Synergy 1.3.7.
I have checked that the server is listening on the correct port by running netstat -ano
. I have also checked that the client can connect to the server on this port with telnet.
The server has the screen name Rupert-PC.
The server is setup with both the server screen, Rupert-PC, and the client screen, Ubuntu.
I have checked that the client is called ubuntu by running hostname
. I have also tried specifying it directly by called synergyc -f --name ubuntu 000.000.000.0
.
However, the client still can't connect and gives the following error:
Error server refused client with name "ubuntu"
Any ideas on what else I can check to get this working?
Edit: I've also tried using Synergy 1.4.3 beta but got the same result.
windows-7 synergy ubuntu-11.04
I'm trying to connect a Windows 7 server and an Ubuntu 11.04 client with Synergy 1.3.7.
I have checked that the server is listening on the correct port by running netstat -ano
. I have also checked that the client can connect to the server on this port with telnet.
The server has the screen name Rupert-PC.
The server is setup with both the server screen, Rupert-PC, and the client screen, Ubuntu.
I have checked that the client is called ubuntu by running hostname
. I have also tried specifying it directly by called synergyc -f --name ubuntu 000.000.000.0
.
However, the client still can't connect and gives the following error:
Error server refused client with name "ubuntu"
Any ideas on what else I can check to get this working?
Edit: I've also tried using Synergy 1.4.3 beta but got the same result.
windows-7 synergy ubuntu-11.04
windows-7 synergy ubuntu-11.04
edited Sep 3 '11 at 7:11
3498DB
15.7k114762
15.7k114762
asked Aug 8 '11 at 23:50
Rupert Madden-Abbott
3123616
3123616
1
The solution was simple: I changed the server screen name from Rupert-PC to rupert. I'm not sure why this worked. Maybe it didn't like the capital letters or the hyphen. Unfortunately I can't add this as an answer for another 8 hours as my reputation is below 100. I'll to remember to do so then.
– Rupert Madden-Abbott
Aug 9 '11 at 0:29
add a comment |
1
The solution was simple: I changed the server screen name from Rupert-PC to rupert. I'm not sure why this worked. Maybe it didn't like the capital letters or the hyphen. Unfortunately I can't add this as an answer for another 8 hours as my reputation is below 100. I'll to remember to do so then.
– Rupert Madden-Abbott
Aug 9 '11 at 0:29
1
1
The solution was simple: I changed the server screen name from Rupert-PC to rupert. I'm not sure why this worked. Maybe it didn't like the capital letters or the hyphen. Unfortunately I can't add this as an answer for another 8 hours as my reputation is below 100. I'll to remember to do so then.
– Rupert Madden-Abbott
Aug 9 '11 at 0:29
The solution was simple: I changed the server screen name from Rupert-PC to rupert. I'm not sure why this worked. Maybe it didn't like the capital letters or the hyphen. Unfortunately I can't add this as an answer for another 8 hours as my reputation is below 100. I'll to remember to do so then.
– Rupert Madden-Abbott
Aug 9 '11 at 0:29
add a comment |
5 Answers
5
active
oldest
votes
The problem is with the hyphen. I was facing the same issue. When I removed the '-' from the client configuration's screen name and from the host's server configuration screen name. It worked.
1
Also remember to stop and start your server after making the change
– Zaptree
Oct 4 '16 at 3:50
add a comment |
The problem was with the server screen name, "Rupert-PC". By using "rupert" instead, synergy worked fine.
This may either be a problem with capitalisation or the hyphen.
add a comment |
I got this to work when I removed special characters from my screen name and made sure I used the same name (client screen name & client name in server).
I was using a Mac as the client (1.4.1) and Windows as the server (1.6.3).
add a comment |
For below setup
- ubuntu 15.04 (acting as server)
- windows 10 (acting as client)
- Synergy 1.7.4 stable version and
- both ubuntu and windows hostnames containing - and capitals
Had to write a configuration file which had both server and client screen names to make this work me. (Also had to kill all synergy processes and restart)
Below is the configuration file content and here's reference link
section: screens
subu:
halfDuplexCapsLock = false
halfDuplexNumLock = false
halfDuplexScrollLock = false
xtestIsXineramaUnaware = false
switchCorners = none
switchCornerSize = 0
swin:
halfDuplexCapsLock = false
halfDuplexNumLock = false
halfDuplexScrollLock = false
xtestIsXineramaUnaware = false
switchCorners = none
switchCornerSize = 0
end
section: aliases
end
section: links
subu:
right = swin
swin:
left = subu
end
section: options
relativeMouseMoves = false
screenSaverSync = true
win32KeepForeground = false
switchCorners = none
switchCornerSize = 0
end
add a comment |
thinks u should be taking care
1.make sure the two systems are in same network (some if u wifi virtualbox adaptor it will take some other ip range)
so u can conform it by changing client to server or vice versa
2.make sure port no are same (default it will be same so u can ignore it if not changed)
3.make sure the screen name is same client and server
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f320646%2fsynergy-1-3-7-server-refused-client-with-our-name%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
The problem is with the hyphen. I was facing the same issue. When I removed the '-' from the client configuration's screen name and from the host's server configuration screen name. It worked.
1
Also remember to stop and start your server after making the change
– Zaptree
Oct 4 '16 at 3:50
add a comment |
The problem is with the hyphen. I was facing the same issue. When I removed the '-' from the client configuration's screen name and from the host's server configuration screen name. It worked.
1
Also remember to stop and start your server after making the change
– Zaptree
Oct 4 '16 at 3:50
add a comment |
The problem is with the hyphen. I was facing the same issue. When I removed the '-' from the client configuration's screen name and from the host's server configuration screen name. It worked.
The problem is with the hyphen. I was facing the same issue. When I removed the '-' from the client configuration's screen name and from the host's server configuration screen name. It worked.
answered Jul 19 '12 at 11:45
Samir
12613
12613
1
Also remember to stop and start your server after making the change
– Zaptree
Oct 4 '16 at 3:50
add a comment |
1
Also remember to stop and start your server after making the change
– Zaptree
Oct 4 '16 at 3:50
1
1
Also remember to stop and start your server after making the change
– Zaptree
Oct 4 '16 at 3:50
Also remember to stop and start your server after making the change
– Zaptree
Oct 4 '16 at 3:50
add a comment |
The problem was with the server screen name, "Rupert-PC". By using "rupert" instead, synergy worked fine.
This may either be a problem with capitalisation or the hyphen.
add a comment |
The problem was with the server screen name, "Rupert-PC". By using "rupert" instead, synergy worked fine.
This may either be a problem with capitalisation or the hyphen.
add a comment |
The problem was with the server screen name, "Rupert-PC". By using "rupert" instead, synergy worked fine.
This may either be a problem with capitalisation or the hyphen.
The problem was with the server screen name, "Rupert-PC". By using "rupert" instead, synergy worked fine.
This may either be a problem with capitalisation or the hyphen.
answered Aug 12 '11 at 13:30
Rupert Madden-Abbott
3123616
3123616
add a comment |
add a comment |
I got this to work when I removed special characters from my screen name and made sure I used the same name (client screen name & client name in server).
I was using a Mac as the client (1.4.1) and Windows as the server (1.6.3).
add a comment |
I got this to work when I removed special characters from my screen name and made sure I used the same name (client screen name & client name in server).
I was using a Mac as the client (1.4.1) and Windows as the server (1.6.3).
add a comment |
I got this to work when I removed special characters from my screen name and made sure I used the same name (client screen name & client name in server).
I was using a Mac as the client (1.4.1) and Windows as the server (1.6.3).
I got this to work when I removed special characters from my screen name and made sure I used the same name (client screen name & client name in server).
I was using a Mac as the client (1.4.1) and Windows as the server (1.6.3).
edited Oct 16 '15 at 20:14
Moses
9,0792158106
9,0792158106
answered Oct 16 '15 at 19:16
Devan Sivaprakasam
111
111
add a comment |
add a comment |
For below setup
- ubuntu 15.04 (acting as server)
- windows 10 (acting as client)
- Synergy 1.7.4 stable version and
- both ubuntu and windows hostnames containing - and capitals
Had to write a configuration file which had both server and client screen names to make this work me. (Also had to kill all synergy processes and restart)
Below is the configuration file content and here's reference link
section: screens
subu:
halfDuplexCapsLock = false
halfDuplexNumLock = false
halfDuplexScrollLock = false
xtestIsXineramaUnaware = false
switchCorners = none
switchCornerSize = 0
swin:
halfDuplexCapsLock = false
halfDuplexNumLock = false
halfDuplexScrollLock = false
xtestIsXineramaUnaware = false
switchCorners = none
switchCornerSize = 0
end
section: aliases
end
section: links
subu:
right = swin
swin:
left = subu
end
section: options
relativeMouseMoves = false
screenSaverSync = true
win32KeepForeground = false
switchCorners = none
switchCornerSize = 0
end
add a comment |
For below setup
- ubuntu 15.04 (acting as server)
- windows 10 (acting as client)
- Synergy 1.7.4 stable version and
- both ubuntu and windows hostnames containing - and capitals
Had to write a configuration file which had both server and client screen names to make this work me. (Also had to kill all synergy processes and restart)
Below is the configuration file content and here's reference link
section: screens
subu:
halfDuplexCapsLock = false
halfDuplexNumLock = false
halfDuplexScrollLock = false
xtestIsXineramaUnaware = false
switchCorners = none
switchCornerSize = 0
swin:
halfDuplexCapsLock = false
halfDuplexNumLock = false
halfDuplexScrollLock = false
xtestIsXineramaUnaware = false
switchCorners = none
switchCornerSize = 0
end
section: aliases
end
section: links
subu:
right = swin
swin:
left = subu
end
section: options
relativeMouseMoves = false
screenSaverSync = true
win32KeepForeground = false
switchCorners = none
switchCornerSize = 0
end
add a comment |
For below setup
- ubuntu 15.04 (acting as server)
- windows 10 (acting as client)
- Synergy 1.7.4 stable version and
- both ubuntu and windows hostnames containing - and capitals
Had to write a configuration file which had both server and client screen names to make this work me. (Also had to kill all synergy processes and restart)
Below is the configuration file content and here's reference link
section: screens
subu:
halfDuplexCapsLock = false
halfDuplexNumLock = false
halfDuplexScrollLock = false
xtestIsXineramaUnaware = false
switchCorners = none
switchCornerSize = 0
swin:
halfDuplexCapsLock = false
halfDuplexNumLock = false
halfDuplexScrollLock = false
xtestIsXineramaUnaware = false
switchCorners = none
switchCornerSize = 0
end
section: aliases
end
section: links
subu:
right = swin
swin:
left = subu
end
section: options
relativeMouseMoves = false
screenSaverSync = true
win32KeepForeground = false
switchCorners = none
switchCornerSize = 0
end
For below setup
- ubuntu 15.04 (acting as server)
- windows 10 (acting as client)
- Synergy 1.7.4 stable version and
- both ubuntu and windows hostnames containing - and capitals
Had to write a configuration file which had both server and client screen names to make this work me. (Also had to kill all synergy processes and restart)
Below is the configuration file content and here's reference link
section: screens
subu:
halfDuplexCapsLock = false
halfDuplexNumLock = false
halfDuplexScrollLock = false
xtestIsXineramaUnaware = false
switchCorners = none
switchCornerSize = 0
swin:
halfDuplexCapsLock = false
halfDuplexNumLock = false
halfDuplexScrollLock = false
xtestIsXineramaUnaware = false
switchCorners = none
switchCornerSize = 0
end
section: aliases
end
section: links
subu:
right = swin
swin:
left = subu
end
section: options
relativeMouseMoves = false
screenSaverSync = true
win32KeepForeground = false
switchCorners = none
switchCornerSize = 0
end
answered Aug 13 '15 at 21:57
sandeepkunkunuru
1012
1012
add a comment |
add a comment |
thinks u should be taking care
1.make sure the two systems are in same network (some if u wifi virtualbox adaptor it will take some other ip range)
so u can conform it by changing client to server or vice versa
2.make sure port no are same (default it will be same so u can ignore it if not changed)
3.make sure the screen name is same client and server
add a comment |
thinks u should be taking care
1.make sure the two systems are in same network (some if u wifi virtualbox adaptor it will take some other ip range)
so u can conform it by changing client to server or vice versa
2.make sure port no are same (default it will be same so u can ignore it if not changed)
3.make sure the screen name is same client and server
add a comment |
thinks u should be taking care
1.make sure the two systems are in same network (some if u wifi virtualbox adaptor it will take some other ip range)
so u can conform it by changing client to server or vice versa
2.make sure port no are same (default it will be same so u can ignore it if not changed)
3.make sure the screen name is same client and server
thinks u should be taking care
1.make sure the two systems are in same network (some if u wifi virtualbox adaptor it will take some other ip range)
so u can conform it by changing client to server or vice versa
2.make sure port no are same (default it will be same so u can ignore it if not changed)
3.make sure the screen name is same client and server
answered Dec 12 '18 at 6:52
Mansoor KN
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f320646%2fsynergy-1-3-7-server-refused-client-with-our-name%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
The solution was simple: I changed the server screen name from Rupert-PC to rupert. I'm not sure why this worked. Maybe it didn't like the capital letters or the hyphen. Unfortunately I can't add this as an answer for another 8 hours as my reputation is below 100. I'll to remember to do so then.
– Rupert Madden-Abbott
Aug 9 '11 at 0:29