Serva Login 0x35 NetPath not found, wrong credentials, or unreliable net
up vote
0
down vote
favorite
I'm trying to install Windows 8 via PXE network boot, I'm using Serva for this.
When I get to the ServaPENet screen on my client I can't connect. Drivers are installed (I tried three different drivers, all should be working), I tried several usernames and passwords (I changed it a few times to make sure it was not due to special characters). All should be working but I still get
0x35 NetPath not found, wrong credentials, or unreliable net.
My server is a laptop connected via wifi and my client is a pc connected via lan.
WIA_WDS is shared as WIA_WDS_SHARE and my server user has access to read. I might have done something wrong in this step, but I also tried several solutions. Can someone give me a step by step tutorial to share this folder correctly?
networking operating-systems
add a comment |
up vote
0
down vote
favorite
I'm trying to install Windows 8 via PXE network boot, I'm using Serva for this.
When I get to the ServaPENet screen on my client I can't connect. Drivers are installed (I tried three different drivers, all should be working), I tried several usernames and passwords (I changed it a few times to make sure it was not due to special characters). All should be working but I still get
0x35 NetPath not found, wrong credentials, or unreliable net.
My server is a laptop connected via wifi and my client is a pc connected via lan.
WIA_WDS is shared as WIA_WDS_SHARE and my server user has access to read. I might have done something wrong in this step, but I also tried several solutions. Can someone give me a step by step tutorial to share this folder correctly?
networking operating-systems
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm trying to install Windows 8 via PXE network boot, I'm using Serva for this.
When I get to the ServaPENet screen on my client I can't connect. Drivers are installed (I tried three different drivers, all should be working), I tried several usernames and passwords (I changed it a few times to make sure it was not due to special characters). All should be working but I still get
0x35 NetPath not found, wrong credentials, or unreliable net.
My server is a laptop connected via wifi and my client is a pc connected via lan.
WIA_WDS is shared as WIA_WDS_SHARE and my server user has access to read. I might have done something wrong in this step, but I also tried several solutions. Can someone give me a step by step tutorial to share this folder correctly?
networking operating-systems
I'm trying to install Windows 8 via PXE network boot, I'm using Serva for this.
When I get to the ServaPENet screen on my client I can't connect. Drivers are installed (I tried three different drivers, all should be working), I tried several usernames and passwords (I changed it a few times to make sure it was not due to special characters). All should be working but I still get
0x35 NetPath not found, wrong credentials, or unreliable net.
My server is a laptop connected via wifi and my client is a pc connected via lan.
WIA_WDS is shared as WIA_WDS_SHARE and my server user has access to read. I might have done something wrong in this step, but I also tried several solutions. Can someone give me a step by step tutorial to share this folder correctly?
networking operating-systems
networking operating-systems
asked Apr 19 '15 at 15:04
TemporaryName
111
111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
error 0x35 is explained on Serva's website
http://vercot.com/~serva/an/WindowsPXE1.html#troubleshooting
8.4.3 WDS OSs ServaPENet login ERROR:0x35:
Microsoft defines error 0x35 (53) as ERROR_BAD_NETPATH and is supposed
to mean "The network path was not found" but in fact it really means a
lot more things.
The error can be triggered in several ways: 1) Network connection
unreliable. 2) WIA_WDS_SHARE bad configured. 3) WIA_WDS_SHARE running
on a very busy/slow/unresponsive server. 4) NIC not working properly.
5) NIC driver not working properly (even if there are no errors). 6)
Wrong login credentials. If your network and server are ok I would
recommend checking the NIC and specially its driver.
There were reported 0x35 errors when installing Vista while the same
client installed Windows 7/8 correctly. On all those cases: 1)
Replacing Vista's sourcesBoot.wim with Windows 7/8
sourcesBoot.wim. 2) Erasing Vista’s SERVA directory. 3) Quit and
restarting Serva. Solved the problem.
In these cases your best bet is start by checking the net driver even if it looks like working ok
Yeah, but nothing there helped me. Everything was fine.. I ended up restarting the server computer, then tried again. Worked the first try. Apparently it had something to do with me changing the password all the time. Also, Serva didn't really like to try again if I had entered the wrong password once, even if I tried again with the correct one, it wouldn't work. I had to get it right on the first try but I didn't realize that, obviously. Thank you anyway.
– TemporaryName
Apr 20 '15 at 14:22
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',
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%2f903450%2fserva-login-0x35-netpath-not-found-wrong-credentials-or-unreliable-net%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
error 0x35 is explained on Serva's website
http://vercot.com/~serva/an/WindowsPXE1.html#troubleshooting
8.4.3 WDS OSs ServaPENet login ERROR:0x35:
Microsoft defines error 0x35 (53) as ERROR_BAD_NETPATH and is supposed
to mean "The network path was not found" but in fact it really means a
lot more things.
The error can be triggered in several ways: 1) Network connection
unreliable. 2) WIA_WDS_SHARE bad configured. 3) WIA_WDS_SHARE running
on a very busy/slow/unresponsive server. 4) NIC not working properly.
5) NIC driver not working properly (even if there are no errors). 6)
Wrong login credentials. If your network and server are ok I would
recommend checking the NIC and specially its driver.
There were reported 0x35 errors when installing Vista while the same
client installed Windows 7/8 correctly. On all those cases: 1)
Replacing Vista's sourcesBoot.wim with Windows 7/8
sourcesBoot.wim. 2) Erasing Vista’s SERVA directory. 3) Quit and
restarting Serva. Solved the problem.
In these cases your best bet is start by checking the net driver even if it looks like working ok
Yeah, but nothing there helped me. Everything was fine.. I ended up restarting the server computer, then tried again. Worked the first try. Apparently it had something to do with me changing the password all the time. Also, Serva didn't really like to try again if I had entered the wrong password once, even if I tried again with the correct one, it wouldn't work. I had to get it right on the first try but I didn't realize that, obviously. Thank you anyway.
– TemporaryName
Apr 20 '15 at 14:22
add a comment |
up vote
0
down vote
error 0x35 is explained on Serva's website
http://vercot.com/~serva/an/WindowsPXE1.html#troubleshooting
8.4.3 WDS OSs ServaPENet login ERROR:0x35:
Microsoft defines error 0x35 (53) as ERROR_BAD_NETPATH and is supposed
to mean "The network path was not found" but in fact it really means a
lot more things.
The error can be triggered in several ways: 1) Network connection
unreliable. 2) WIA_WDS_SHARE bad configured. 3) WIA_WDS_SHARE running
on a very busy/slow/unresponsive server. 4) NIC not working properly.
5) NIC driver not working properly (even if there are no errors). 6)
Wrong login credentials. If your network and server are ok I would
recommend checking the NIC and specially its driver.
There were reported 0x35 errors when installing Vista while the same
client installed Windows 7/8 correctly. On all those cases: 1)
Replacing Vista's sourcesBoot.wim with Windows 7/8
sourcesBoot.wim. 2) Erasing Vista’s SERVA directory. 3) Quit and
restarting Serva. Solved the problem.
In these cases your best bet is start by checking the net driver even if it looks like working ok
Yeah, but nothing there helped me. Everything was fine.. I ended up restarting the server computer, then tried again. Worked the first try. Apparently it had something to do with me changing the password all the time. Also, Serva didn't really like to try again if I had entered the wrong password once, even if I tried again with the correct one, it wouldn't work. I had to get it right on the first try but I didn't realize that, obviously. Thank you anyway.
– TemporaryName
Apr 20 '15 at 14:22
add a comment |
up vote
0
down vote
up vote
0
down vote
error 0x35 is explained on Serva's website
http://vercot.com/~serva/an/WindowsPXE1.html#troubleshooting
8.4.3 WDS OSs ServaPENet login ERROR:0x35:
Microsoft defines error 0x35 (53) as ERROR_BAD_NETPATH and is supposed
to mean "The network path was not found" but in fact it really means a
lot more things.
The error can be triggered in several ways: 1) Network connection
unreliable. 2) WIA_WDS_SHARE bad configured. 3) WIA_WDS_SHARE running
on a very busy/slow/unresponsive server. 4) NIC not working properly.
5) NIC driver not working properly (even if there are no errors). 6)
Wrong login credentials. If your network and server are ok I would
recommend checking the NIC and specially its driver.
There were reported 0x35 errors when installing Vista while the same
client installed Windows 7/8 correctly. On all those cases: 1)
Replacing Vista's sourcesBoot.wim with Windows 7/8
sourcesBoot.wim. 2) Erasing Vista’s SERVA directory. 3) Quit and
restarting Serva. Solved the problem.
In these cases your best bet is start by checking the net driver even if it looks like working ok
error 0x35 is explained on Serva's website
http://vercot.com/~serva/an/WindowsPXE1.html#troubleshooting
8.4.3 WDS OSs ServaPENet login ERROR:0x35:
Microsoft defines error 0x35 (53) as ERROR_BAD_NETPATH and is supposed
to mean "The network path was not found" but in fact it really means a
lot more things.
The error can be triggered in several ways: 1) Network connection
unreliable. 2) WIA_WDS_SHARE bad configured. 3) WIA_WDS_SHARE running
on a very busy/slow/unresponsive server. 4) NIC not working properly.
5) NIC driver not working properly (even if there are no errors). 6)
Wrong login credentials. If your network and server are ok I would
recommend checking the NIC and specially its driver.
There were reported 0x35 errors when installing Vista while the same
client installed Windows 7/8 correctly. On all those cases: 1)
Replacing Vista's sourcesBoot.wim with Windows 7/8
sourcesBoot.wim. 2) Erasing Vista’s SERVA directory. 3) Quit and
restarting Serva. Solved the problem.
In these cases your best bet is start by checking the net driver even if it looks like working ok
answered Apr 19 '15 at 17:47
Pat
2,4941021
2,4941021
Yeah, but nothing there helped me. Everything was fine.. I ended up restarting the server computer, then tried again. Worked the first try. Apparently it had something to do with me changing the password all the time. Also, Serva didn't really like to try again if I had entered the wrong password once, even if I tried again with the correct one, it wouldn't work. I had to get it right on the first try but I didn't realize that, obviously. Thank you anyway.
– TemporaryName
Apr 20 '15 at 14:22
add a comment |
Yeah, but nothing there helped me. Everything was fine.. I ended up restarting the server computer, then tried again. Worked the first try. Apparently it had something to do with me changing the password all the time. Also, Serva didn't really like to try again if I had entered the wrong password once, even if I tried again with the correct one, it wouldn't work. I had to get it right on the first try but I didn't realize that, obviously. Thank you anyway.
– TemporaryName
Apr 20 '15 at 14:22
Yeah, but nothing there helped me. Everything was fine.. I ended up restarting the server computer, then tried again. Worked the first try. Apparently it had something to do with me changing the password all the time. Also, Serva didn't really like to try again if I had entered the wrong password once, even if I tried again with the correct one, it wouldn't work. I had to get it right on the first try but I didn't realize that, obviously. Thank you anyway.
– TemporaryName
Apr 20 '15 at 14:22
Yeah, but nothing there helped me. Everything was fine.. I ended up restarting the server computer, then tried again. Worked the first try. Apparently it had something to do with me changing the password all the time. Also, Serva didn't really like to try again if I had entered the wrong password once, even if I tried again with the correct one, it wouldn't work. I had to get it right on the first try but I didn't realize that, obviously. Thank you anyway.
– TemporaryName
Apr 20 '15 at 14:22
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%2f903450%2fserva-login-0x35-netpath-not-found-wrong-credentials-or-unreliable-net%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