My PC is not reachable on local LAN after changing computer name
My PC is not reachable on my local LAN (workgroup) after changing the computer name. I then renamed it back to the original name and it is still not reachable.
Pinging other computers from mine is successful. However, other computers can't ping me or access my shared folders.
What do you suggest in that case?
windows networking lan workgroup
edited Oct 8 '12 at 0:00
Indrek
20.6k117484
migrated from stackoverflow.com Apr 4 '12 at 17:51
This question came from our site for professional and enthusiast programmers.
add a comment |
My PC is not reachable on my local LAN (workgroup) after changing the computer name. I then renamed it back to the original name and it is still not reachable.
Pinging other computers from mine is successful. However, other computers can't ping me or access my shared folders.
What do you suggest in that case?
windows networking lan workgroup
edited Oct 8 '12 at 0:00
Indrek
20.6k117484
migrated from stackoverflow.com Apr 4 '12 at 17:51
This question came from our site for professional and enthusiast programmers.
are you part of the same workgroup, domain, or use the same gateway?
– datatoo
Apr 5 '12 at 1:41
add a comment |
My PC is not reachable on my local LAN (workgroup) after changing the computer name. I then renamed it back to the original name and it is still not reachable.
Pinging other computers from mine is successful. However, other computers can't ping me or access my shared folders.
What do you suggest in that case?
windows networking lan workgroup
edited Oct 8 '12 at 0:00
Indrek
20.6k117484
My PC is not reachable on my local LAN (workgroup) after changing the computer name. I then renamed it back to the original name and it is still not reachable.
Pinging other computers from mine is successful. However, other computers can't ping me or access my shared folders.
What do you suggest in that case?
windows networking lan workgroup
windows networking lan workgroup
edited Oct 8 '12 at 0:00
Indrek
20.6k117484
edited Oct 8 '12 at 0:00
Indrek
20.6k117484
edited Oct 8 '12 at 0:00
Indrek
20.6k117484
edited Oct 8 '12 at 0:00
Indrek
20.6k117484
edited Oct 8 '12 at 0:00
Indrek
20.6k117484
20.6k117484
asked Apr 4 '12 at 16:24
Skystar3
migrated from stackoverflow.com Apr 4 '12 at 17:51
This question came from our site for professional and enthusiast programmers.
migrated from stackoverflow.com Apr 4 '12 at 17:51
This question came from our site for professional and enthusiast programmers.
are you part of the same workgroup, domain, or use the same gateway?
– datatoo
Apr 5 '12 at 1:41
add a comment |
are you part of the same workgroup, domain, or use the same gateway?
– datatoo
Apr 5 '12 at 1:41
are you part of the same workgroup, domain, or use the same gateway?
– datatoo
Apr 5 '12 at 1:41
are you part of the same workgroup, domain, or use the same gateway?
– datatoo
Apr 5 '12 at 1:41
add a comment |
2 Answers
2
active
oldest
votes
The other computers may have dns entries cached. This would be one reason why your PC can see others, but not the other way around.
One thing you will want to try is a dns flush on the other computers. If these are windows machines, you will want to go to start / run / cmd. Once at the command prompt type ipconfig /flushdns .
Is the hostname the only thing that was changed? Are there any new firewall programs installed, or the Windows firewall enabled?
answered Apr 4 '12 at 18:19
pextrispextris
35128
IMO, computers in a Windows workgroup do not require DNS for identification and communication. They are using NetBIOS names. Were computers required DNS to communicate in a workgroup, that would have made impossible inter-process communication inside the same computer, i.e. functioning of isolated computer at all (without setting a local DNS server on a workstation first)
– Gennady Vanin Геннадий Ванин
Apr 30 '12 at 4:07
add a comment |
I do not think that changing computer (or workgroup) name makes computer unreachable by its ip-address.
Returning a computer the previous name never recovers the same computer SID, i.e. after getting the same name the identification of computer is different.
All users in a workgroup are identified as (computer ID)username and so, effectively, they and access to any network shared resource (service, file, etc.) under those IDs (accounts, users) were reset.
I would reboot computer after changing computer (or user/account) name and reset/reinstall anew any network shared resource (network printers, network shares, shared network services, etc.) that depend on any such usernames with corresponding reboot on any other computers.
IMO, such changes require some time to propagate and are not immediate and require up to 2 hours to be known by (sychronized at) other computers in workgroup
answered Apr 30 '12 at 3:57
Gennady Vanin Геннадий ВанинGennady Vanin Геннадий Ванин
36021027
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%2f408612%2fmy-pc-is-not-reachable-on-local-lan-after-changing-computer-name%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The other computers may have dns entries cached. This would be one reason why your PC can see others, but not the other way around.
One thing you will want to try is a dns flush on the other computers. If these are windows machines, you will want to go to start / run / cmd. Once at the command prompt type ipconfig /flushdns .
Is the hostname the only thing that was changed? Are there any new firewall programs installed, or the Windows firewall enabled?
answered Apr 4 '12 at 18:19
pextrispextris
35128
IMO, computers in a Windows workgroup do not require DNS for identification and communication. They are using NetBIOS names. Were computers required DNS to communicate in a workgroup, that would have made impossible inter-process communication inside the same computer, i.e. functioning of isolated computer at all (without setting a local DNS server on a workstation first)
– Gennady Vanin Геннадий Ванин
Apr 30 '12 at 4:07
add a comment |
The other computers may have dns entries cached. This would be one reason why your PC can see others, but not the other way around.
One thing you will want to try is a dns flush on the other computers. If these are windows machines, you will want to go to start / run / cmd. Once at the command prompt type ipconfig /flushdns .
Is the hostname the only thing that was changed? Are there any new firewall programs installed, or the Windows firewall enabled?
answered Apr 4 '12 at 18:19
pextrispextris
35128
IMO, computers in a Windows workgroup do not require DNS for identification and communication. They are using NetBIOS names. Were computers required DNS to communicate in a workgroup, that would have made impossible inter-process communication inside the same computer, i.e. functioning of isolated computer at all (without setting a local DNS server on a workstation first)
– Gennady Vanin Геннадий Ванин
Apr 30 '12 at 4:07
add a comment |
The other computers may have dns entries cached. This would be one reason why your PC can see others, but not the other way around.
One thing you will want to try is a dns flush on the other computers. If these are windows machines, you will want to go to start / run / cmd. Once at the command prompt type ipconfig /flushdns .
Is the hostname the only thing that was changed? Are there any new firewall programs installed, or the Windows firewall enabled?
answered Apr 4 '12 at 18:19
pextrispextris
35128
The other computers may have dns entries cached. This would be one reason why your PC can see others, but not the other way around.
One thing you will want to try is a dns flush on the other computers. If these are windows machines, you will want to go to start / run / cmd. Once at the command prompt type ipconfig /flushdns .
Is the hostname the only thing that was changed? Are there any new firewall programs installed, or the Windows firewall enabled?
answered Apr 4 '12 at 18:19
pextrispextris
35128
answered Apr 4 '12 at 18:19
pextrispextris
35128
answered Apr 4 '12 at 18:19
pextrispextris
35128
answered Apr 4 '12 at 18:19
pextrispextris
35128
35128
IMO, computers in a Windows workgroup do not require DNS for identification and communication. They are using NetBIOS names. Were computers required DNS to communicate in a workgroup, that would have made impossible inter-process communication inside the same computer, i.e. functioning of isolated computer at all (without setting a local DNS server on a workstation first)
– Gennady Vanin Геннадий Ванин
Apr 30 '12 at 4:07
add a comment |
IMO, computers in a Windows workgroup do not require DNS for identification and communication. They are using NetBIOS names. Were computers required DNS to communicate in a workgroup, that would have made impossible inter-process communication inside the same computer, i.e. functioning of isolated computer at all (without setting a local DNS server on a workstation first)
– Gennady Vanin Геннадий Ванин
Apr 30 '12 at 4:07
IMO, computers in a Windows workgroup do not require DNS for identification and communication. They are using NetBIOS names. Were computers required DNS to communicate in a workgroup, that would have made impossible inter-process communication inside the same computer, i.e. functioning of isolated computer at all (without setting a local DNS server on a workstation first)
– Gennady Vanin Геннадий Ванин
Apr 30 '12 at 4:07
IMO, computers in a Windows workgroup do not require DNS for identification and communication. They are using NetBIOS names. Were computers required DNS to communicate in a workgroup, that would have made impossible inter-process communication inside the same computer, i.e. functioning of isolated computer at all (without setting a local DNS server on a workstation first)
– Gennady Vanin Геннадий Ванин
Apr 30 '12 at 4:07
add a comment |
I do not think that changing computer (or workgroup) name makes computer unreachable by its ip-address.
Returning a computer the previous name never recovers the same computer SID, i.e. after getting the same name the identification of computer is different.
All users in a workgroup are identified as (computer ID)username and so, effectively, they and access to any network shared resource (service, file, etc.) under those IDs (accounts, users) were reset.
I would reboot computer after changing computer (or user/account) name and reset/reinstall anew any network shared resource (network printers, network shares, shared network services, etc.) that depend on any such usernames with corresponding reboot on any other computers.
IMO, such changes require some time to propagate and are not immediate and require up to 2 hours to be known by (sychronized at) other computers in workgroup
answered Apr 30 '12 at 3:57
Gennady Vanin Геннадий ВанинGennady Vanin Геннадий Ванин
36021027
add a comment |
I do not think that changing computer (or workgroup) name makes computer unreachable by its ip-address.
Returning a computer the previous name never recovers the same computer SID, i.e. after getting the same name the identification of computer is different.
All users in a workgroup are identified as (computer ID)username and so, effectively, they and access to any network shared resource (service, file, etc.) under those IDs (accounts, users) were reset.
I would reboot computer after changing computer (or user/account) name and reset/reinstall anew any network shared resource (network printers, network shares, shared network services, etc.) that depend on any such usernames with corresponding reboot on any other computers.
IMO, such changes require some time to propagate and are not immediate and require up to 2 hours to be known by (sychronized at) other computers in workgroup
answered Apr 30 '12 at 3:57
Gennady Vanin Геннадий ВанинGennady Vanin Геннадий Ванин
36021027
add a comment |
I do not think that changing computer (or workgroup) name makes computer unreachable by its ip-address.
Returning a computer the previous name never recovers the same computer SID, i.e. after getting the same name the identification of computer is different.
All users in a workgroup are identified as (computer ID)username and so, effectively, they and access to any network shared resource (service, file, etc.) under those IDs (accounts, users) were reset.
I would reboot computer after changing computer (or user/account) name and reset/reinstall anew any network shared resource (network printers, network shares, shared network services, etc.) that depend on any such usernames with corresponding reboot on any other computers.
IMO, such changes require some time to propagate and are not immediate and require up to 2 hours to be known by (sychronized at) other computers in workgroup
answered Apr 30 '12 at 3:57
Gennady Vanin Геннадий ВанинGennady Vanin Геннадий Ванин
36021027
I do not think that changing computer (or workgroup) name makes computer unreachable by its ip-address.
Returning a computer the previous name never recovers the same computer SID, i.e. after getting the same name the identification of computer is different.
All users in a workgroup are identified as (computer ID)username and so, effectively, they and access to any network shared resource (service, file, etc.) under those IDs (accounts, users) were reset.
I would reboot computer after changing computer (or user/account) name and reset/reinstall anew any network shared resource (network printers, network shares, shared network services, etc.) that depend on any such usernames with corresponding reboot on any other computers.
IMO, such changes require some time to propagate and are not immediate and require up to 2 hours to be known by (sychronized at) other computers in workgroup
answered Apr 30 '12 at 3:57
Gennady Vanin Геннадий ВанинGennady Vanin Геннадий Ванин
36021027
answered Apr 30 '12 at 3:57
Gennady Vanin Геннадий ВанинGennady Vanin Геннадий Ванин
36021027
answered Apr 30 '12 at 3:57
Gennady Vanin Геннадий ВанинGennady Vanin Геннадий Ванин
36021027
answered Apr 30 '12 at 3:57
Gennady Vanin Геннадий ВанинGennady Vanin Геннадий Ванин
36021027
36021027
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.
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%2f408612%2fmy-pc-is-not-reachable-on-local-lan-after-changing-computer-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
are you part of the same workgroup, domain, or use the same gateway?
– datatoo
Apr 5 '12 at 1:41