Pxe Net Use Error 53
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sun, 23 Oct 2016 11:02:28 GMT by s_ac4 (squid/3.5.20)
You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. NET USE command over http (external ip, not LAN) ---> error 53 Started by 69jakk , Jan 06 http://reboot.pro/topic/17956-net-use-command-over-http-external-ip-not-lan-error-53/ 2013 10:22 AM net use pxe http error 53 path not found Best Answer andriusst , 06 January 2013 - 11:50 PM hi 69jakk Internet providers usually block Netbios and windows sharing traffic http://serverfault.com/questions/622269/cant-connect-to-deploymentshare-from-pc-attempting-to-mdt-but-can-other-pcs-o to reduce virus spreading. There are several other ways you can try accessing your share but anything that comes to mind will require adding additional components into your PE image. 1. some sort error 5 of tunnelling solution between your server and client PC. Perhaps OpenVPN. Map network drive over that. 2. httpdisk driver. Put windows installation ISO on your www server and mount it as a disk and do installation. maybe someone else will have further suggestions. good luck. Go to the full post
Page 1 of 2 1 2 Next Please log in to reply 32 replies to this topic system error 5 #1 69jakk 69jakk Member Members 46 posts Spain Posted 06 January 2013 - 10:22 AM Hi everyone! I'm trying to deploy Windows 7 over http with gpxe, wimboot and a Windows XP SP3 with Apache as Server. I'm have tried to deploy Windows 7 over LAN with the following command after booting Win7Pe with wimboot: NET USE Z: \\My_Server_IP\Network_Share USER:/My_Server_IP\User Password And everything works fine but this is over LAN method...and I'm interested in over WAN method. I mean, net use command from an external ip not local. So I use the same command with the following results:NET USE Z: \\My_Server_IP\Network_Share USER:/My_Server_IP\User Password System error 53. The network path was not found Does anyone know what could be the problem? I have activated NETBIOS over TCP option on Network connections and open ports 139 and 145 on the router connected to the server so it should allow the incoming traffic... Any ideas or help would be really appreciated. Greets Edited by 69jakk, 06 January 2013 - 10:24 AM. Back to top #2 DarkPhoeniX DarkPhoeniX Frequent Member Team Reboot 452 posts Location:In the middle of nowhere Interests:Interesting Things South Africa Posted 06 January 2013 - 11:21 AM I never try'd PXE oveStart here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Can't connect to DeploymentShare$ from PC attempting to MDT, but can other PCs on the network up vote 0 down vote favorite I am in the process of setting up MDT and have run across a problem. MDT is installed on a Windows 2012 server, MDT version 6.2.5019.0. Using WDS as well. Active Directory domain, the server is up to date and on the network. I boot up the PC, it gets an address from DHCP, pulls down the LiteTouchPE_x64.wim image and goes into the MS Solution Accelerators screen, the Processing Bootstrap Settings box comes up and processes for a couple of seconds, then goes away, it sits there for another minute or so and then gives the error: A connection to the deployment share (\\Acme-MDT\DeploymentShare$) could not be made. Can not reach the DeployRoot. Possible Cause: Network Routing error or Network Configuration Error." I can then retry or cancel. I have seen this error online but so far nothing that helps fix it, but seems to be an issue with the FQDN. I verified that I am getting an IP address and that I can successfully ping the MDT server if I use the FQDN, but can not just by it's A record of Acme-MDT. I tried manually mapping the network share using net use and it works if I use the FQDN, but it fails with an error code 53, "Network path not found" if I just use the A record of Acme-MDT. Here is the net use command I'm using: net use * \\Acme-MDT\DeploymentShare$ /u:Domain\Administrator It gives the error System Error 53, Network path not found (and doesn't prompt for a password), but if I use the FQDN of \\Acme-MDT.domain.com\DeploymentShare$ it works fine to map the drive. I guess the problem is, when it tries to load the image, it is trying to start from \\Acme-MDT\Deployme