3D scanner needs PC with static IP?
A 3D scanner here needs to be connected to a PC with a static IP address.
The PC is connected to small Windows workgroup.
Would you:
a) Give the PC a static IP address from within Windows 10
OR
b) Give the PC a static IP using by reserving its IP in the router
windows networking
asked Jan 22 at 23:17
daikindaikin
982
add a comment |
A 3D scanner here needs to be connected to a PC with a static IP address.
The PC is connected to small Windows workgroup.
Would you:
a) Give the PC a static IP address from within Windows 10
OR
b) Give the PC a static IP using by reserving its IP in the router
windows networking
asked Jan 22 at 23:17
daikindaikin
982
5
This reads like a homework question.
– fixer1234
Jan 23 at 0:39
add a comment |
A 3D scanner here needs to be connected to a PC with a static IP address.
The PC is connected to small Windows workgroup.
Would you:
a) Give the PC a static IP address from within Windows 10
OR
b) Give the PC a static IP using by reserving its IP in the router
windows networking
asked Jan 22 at 23:17
daikindaikin
982
A 3D scanner here needs to be connected to a PC with a static IP address.
The PC is connected to small Windows workgroup.
Would you:
a) Give the PC a static IP address from within Windows 10
OR
b) Give the PC a static IP using by reserving its IP in the router
windows networking
windows networking
asked Jan 22 at 23:17
daikindaikin
982
asked Jan 22 at 23:17
daikindaikin
982
asked Jan 22 at 23:17
daikindaikin
982
asked Jan 22 at 23:17
daikindaikin
982
asked Jan 22 at 23:17
daikindaikin
982
982
5
This reads like a homework question.
– fixer1234
Jan 23 at 0:39
add a comment |
5
This reads like a homework question.
– fixer1234
Jan 23 at 0:39
5
5
This reads like a homework question.
– fixer1234
Jan 23 at 0:39
This reads like a homework question.
– fixer1234
Jan 23 at 0:39
add a comment |
2 Answers
2
active
oldest
votes
In a home environment, I prefer to assign a static IP. It's quick and easy.
In a business environment, I prefer to use a reserved address via DHCP. If and when other components of the network infrastructure change, like the DNS servers or the gateway, it is easier to deploy the new values to multiple clients if the clients themselves are already configured to use DHCP for their configuration needs.
answered Jan 22 at 23:30
Doug DedenDoug Deden
49728
5
Amen to that. Even for a home-setup I would go the DHCP route. Just so the DHCP server (in the router) knows which ip-adddress are reserved for those "special" devices. In most home-routers this will also automatically create a DNS entry for the device with the reserved address in its local DNS database. This may greatly improve name-based lookups in the local LAN, so you don't need to rely solely on the (often flaky) broadcast or WINS mechanisms of Windows.
– Tonny
Jan 22 at 23:50
1
Agree on that with @Tonny. Using a static IP can cause problems on the long term if the component is disconnected enough time to get its IP lease time expired and other device coincidentally gets the same IP. You can assign an IP outside the DHCP range, but in my opinion is unconvenient to remember that for the next network changes, and if you are already connecting to the router, why not use DHCP reservations and forget about it.
– Igb
Jan 23 at 23:41
thanks for the responses!
– daikin
Jan 24 at 11:58
add a comment |
Another option would be to setup an individual network between your PC and printer. This is useful when:
- You do not wish to alter, or have control over configurations of your existing network.
- The printer, or whatever the device is, always communicate with one specific PC
Buy a new network card (USB-LAN adapter would suffice), install it on your PC, configure it to have a static IP. The configuration of other card(currently in use) and rest of network should remain as-is.
answered Jan 23 at 4:51
user6493398user6493398
34
thanks for the responses!
– daikin
Jan 24 at 11:58
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%2f1397210%2f3d-scanner-needs-pc-with-static-ip%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
In a home environment, I prefer to assign a static IP. It's quick and easy.
In a business environment, I prefer to use a reserved address via DHCP. If and when other components of the network infrastructure change, like the DNS servers or the gateway, it is easier to deploy the new values to multiple clients if the clients themselves are already configured to use DHCP for their configuration needs.
answered Jan 22 at 23:30
Doug DedenDoug Deden
49728
5
Amen to that. Even for a home-setup I would go the DHCP route. Just so the DHCP server (in the router) knows which ip-adddress are reserved for those "special" devices. In most home-routers this will also automatically create a DNS entry for the device with the reserved address in its local DNS database. This may greatly improve name-based lookups in the local LAN, so you don't need to rely solely on the (often flaky) broadcast or WINS mechanisms of Windows.
– Tonny
Jan 22 at 23:50
1
Agree on that with @Tonny. Using a static IP can cause problems on the long term if the component is disconnected enough time to get its IP lease time expired and other device coincidentally gets the same IP. You can assign an IP outside the DHCP range, but in my opinion is unconvenient to remember that for the next network changes, and if you are already connecting to the router, why not use DHCP reservations and forget about it.
– Igb
Jan 23 at 23:41
thanks for the responses!
– daikin
Jan 24 at 11:58
add a comment |
In a home environment, I prefer to assign a static IP. It's quick and easy.
In a business environment, I prefer to use a reserved address via DHCP. If and when other components of the network infrastructure change, like the DNS servers or the gateway, it is easier to deploy the new values to multiple clients if the clients themselves are already configured to use DHCP for their configuration needs.
answered Jan 22 at 23:30
Doug DedenDoug Deden
49728
5
Amen to that. Even for a home-setup I would go the DHCP route. Just so the DHCP server (in the router) knows which ip-adddress are reserved for those "special" devices. In most home-routers this will also automatically create a DNS entry for the device with the reserved address in its local DNS database. This may greatly improve name-based lookups in the local LAN, so you don't need to rely solely on the (often flaky) broadcast or WINS mechanisms of Windows.
– Tonny
Jan 22 at 23:50
1
Agree on that with @Tonny. Using a static IP can cause problems on the long term if the component is disconnected enough time to get its IP lease time expired and other device coincidentally gets the same IP. You can assign an IP outside the DHCP range, but in my opinion is unconvenient to remember that for the next network changes, and if you are already connecting to the router, why not use DHCP reservations and forget about it.
– Igb
Jan 23 at 23:41
thanks for the responses!
– daikin
Jan 24 at 11:58
add a comment |
In a home environment, I prefer to assign a static IP. It's quick and easy.
In a business environment, I prefer to use a reserved address via DHCP. If and when other components of the network infrastructure change, like the DNS servers or the gateway, it is easier to deploy the new values to multiple clients if the clients themselves are already configured to use DHCP for their configuration needs.
answered Jan 22 at 23:30
Doug DedenDoug Deden
49728
In a home environment, I prefer to assign a static IP. It's quick and easy.
In a business environment, I prefer to use a reserved address via DHCP. If and when other components of the network infrastructure change, like the DNS servers or the gateway, it is easier to deploy the new values to multiple clients if the clients themselves are already configured to use DHCP for their configuration needs.
answered Jan 22 at 23:30
Doug DedenDoug Deden
49728
answered Jan 22 at 23:30
Doug DedenDoug Deden
49728
answered Jan 22 at 23:30
Doug DedenDoug Deden
49728
answered Jan 22 at 23:30
Doug DedenDoug Deden
49728
49728
5
Amen to that. Even for a home-setup I would go the DHCP route. Just so the DHCP server (in the router) knows which ip-adddress are reserved for those "special" devices. In most home-routers this will also automatically create a DNS entry for the device with the reserved address in its local DNS database. This may greatly improve name-based lookups in the local LAN, so you don't need to rely solely on the (often flaky) broadcast or WINS mechanisms of Windows.
– Tonny
Jan 22 at 23:50
1
Agree on that with @Tonny. Using a static IP can cause problems on the long term if the component is disconnected enough time to get its IP lease time expired and other device coincidentally gets the same IP. You can assign an IP outside the DHCP range, but in my opinion is unconvenient to remember that for the next network changes, and if you are already connecting to the router, why not use DHCP reservations and forget about it.
– Igb
Jan 23 at 23:41
thanks for the responses!
– daikin
Jan 24 at 11:58
add a comment |
5
Amen to that. Even for a home-setup I would go the DHCP route. Just so the DHCP server (in the router) knows which ip-adddress are reserved for those "special" devices. In most home-routers this will also automatically create a DNS entry for the device with the reserved address in its local DNS database. This may greatly improve name-based lookups in the local LAN, so you don't need to rely solely on the (often flaky) broadcast or WINS mechanisms of Windows.
– Tonny
Jan 22 at 23:50
1
Agree on that with @Tonny. Using a static IP can cause problems on the long term if the component is disconnected enough time to get its IP lease time expired and other device coincidentally gets the same IP. You can assign an IP outside the DHCP range, but in my opinion is unconvenient to remember that for the next network changes, and if you are already connecting to the router, why not use DHCP reservations and forget about it.
– Igb
Jan 23 at 23:41
thanks for the responses!
– daikin
Jan 24 at 11:58
5
5
Amen to that. Even for a home-setup I would go the DHCP route. Just so the DHCP server (in the router) knows which ip-adddress are reserved for those "special" devices. In most home-routers this will also automatically create a DNS entry for the device with the reserved address in its local DNS database. This may greatly improve name-based lookups in the local LAN, so you don't need to rely solely on the (often flaky) broadcast or WINS mechanisms of Windows.
– Tonny
Jan 22 at 23:50
Amen to that. Even for a home-setup I would go the DHCP route. Just so the DHCP server (in the router) knows which ip-adddress are reserved for those "special" devices. In most home-routers this will also automatically create a DNS entry for the device with the reserved address in its local DNS database. This may greatly improve name-based lookups in the local LAN, so you don't need to rely solely on the (often flaky) broadcast or WINS mechanisms of Windows.
– Tonny
Jan 22 at 23:50
1
1
Agree on that with @Tonny. Using a static IP can cause problems on the long term if the component is disconnected enough time to get its IP lease time expired and other device coincidentally gets the same IP. You can assign an IP outside the DHCP range, but in my opinion is unconvenient to remember that for the next network changes, and if you are already connecting to the router, why not use DHCP reservations and forget about it.
– Igb
Jan 23 at 23:41
Agree on that with @Tonny. Using a static IP can cause problems on the long term if the component is disconnected enough time to get its IP lease time expired and other device coincidentally gets the same IP. You can assign an IP outside the DHCP range, but in my opinion is unconvenient to remember that for the next network changes, and if you are already connecting to the router, why not use DHCP reservations and forget about it.
– Igb
Jan 23 at 23:41
thanks for the responses!
– daikin
Jan 24 at 11:58
thanks for the responses!
– daikin
Jan 24 at 11:58
add a comment |
Another option would be to setup an individual network between your PC and printer. This is useful when:
- You do not wish to alter, or have control over configurations of your existing network.
- The printer, or whatever the device is, always communicate with one specific PC
Buy a new network card (USB-LAN adapter would suffice), install it on your PC, configure it to have a static IP. The configuration of other card(currently in use) and rest of network should remain as-is.
answered Jan 23 at 4:51
user6493398user6493398
34
thanks for the responses!
– daikin
Jan 24 at 11:58
add a comment |
Another option would be to setup an individual network between your PC and printer. This is useful when:
- You do not wish to alter, or have control over configurations of your existing network.
- The printer, or whatever the device is, always communicate with one specific PC
Buy a new network card (USB-LAN adapter would suffice), install it on your PC, configure it to have a static IP. The configuration of other card(currently in use) and rest of network should remain as-is.
answered Jan 23 at 4:51
user6493398user6493398
34
thanks for the responses!
– daikin
Jan 24 at 11:58
add a comment |
Another option would be to setup an individual network between your PC and printer. This is useful when:
- You do not wish to alter, or have control over configurations of your existing network.
- The printer, or whatever the device is, always communicate with one specific PC
Buy a new network card (USB-LAN adapter would suffice), install it on your PC, configure it to have a static IP. The configuration of other card(currently in use) and rest of network should remain as-is.
answered Jan 23 at 4:51
user6493398user6493398
34
Another option would be to setup an individual network between your PC and printer. This is useful when:
- You do not wish to alter, or have control over configurations of your existing network.
- The printer, or whatever the device is, always communicate with one specific PC
Buy a new network card (USB-LAN adapter would suffice), install it on your PC, configure it to have a static IP. The configuration of other card(currently in use) and rest of network should remain as-is.
answered Jan 23 at 4:51
user6493398user6493398
34
edited Jan 23 at 23:33
answered Jan 23 at 4:51
user6493398user6493398
34
answered Jan 23 at 4:51
user6493398user6493398
34
answered Jan 23 at 4:51
user6493398user6493398
34
34
thanks for the responses!
– daikin
Jan 24 at 11:58
add a comment |
thanks for the responses!
– daikin
Jan 24 at 11:58
thanks for the responses!
– daikin
Jan 24 at 11:58
thanks for the responses!
– daikin
Jan 24 at 11:58
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%2f1397210%2f3d-scanner-needs-pc-with-static-ip%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
5
This reads like a homework question.
– fixer1234
Jan 23 at 0:39