I apologize ahead of time, I am new to networking and I obviously don't understand everything yet. Please have mercy on me.
Host is supermicro server running windows 10 pro build 19044.1466. The client is a random HP laptop that has pxe booted a custom windows PE image from the host (Could a mismatch in windows PE and windows 10 cause the two to not communicate?). I am designing a script which performs a task on any laptop plugged into a switch which is plugged into my host (with ethernet cables) and then sends a pdf report to the host. I want to use the net use command to map the network drive automatically on startup so I can automatically send the pdf report to the host after completion of the script. Before I build the script I wanted to test network connectivity and see if I can view the network folder in the command line. So I used the net view command to see if my shared network folder showed up on my network. The command returned the "system error 1231" error.
Below are the things I have tried thus far:
- I made sure the computers were on the same network. The host computer has a IP address of 192.168.1.10. The client has a IP address of 192.168.1.51. The host computer has a static IP address and the clients use DHCP to automatically assign IP addresses. I checked that the subnet masks match and they do (both are 255.255.255.0). There is no router because this is a point to point LAN consisting of just the host, a switch and clients. The network is not connected to the wider internet and is isolated.
- I next checked to see if I could ping the server from the client and I could not. I took down the firewall and that did not resolve the issue. The error I received when I tried to ping the server was "Ping, transmit failed, general failure". I next flushed my DNS cache and now I can ping the server. However, the net view command still does not work.
- I went into the network and sharing center to the advanced sharing settings and made sure the "private", "public" and "all networks" settings for printers and network discovery were turned on.
- Next I went back to google and read a ton of articles (I had already read a ton of articles at this point), I checked to see if the computers were in the same workgroup. They were in the same workgroup.
- I tried every variant of the net view command: NET VIEW, NET VIEW /ALL, net view /all. All of these returned the same error listed above.
- I next tried starting the service Webclient, sadly this was ineffective.
- I turned SMBv1 on. Still no effect.
- I made sure my machine name was all upper case letters. No effect on net view.
- I tried the following commands: ipconfig /flushdns
nbtstat -R
nbtstat -RR
netsh int reset all
netsh int ip reset
netsh winsock reset
From the article I read these commands were supposed to reset TCP/IP stack.
The "netsh int reset all" command had a response along the lines of "command not found". All the rest worked. I then restarted the server and tried again. The net view command still did not work. I checked the IP settings and changed the IP settings back to the static IP I used before (192.168.1.10). The net view command still would not work.
- Next I created a .bat script which is as follows
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi sc.exe config mrxsmb20 start= disabled. I proceeded to run this script as a administrator. To my despair, this script did nothing to solve this problem.
- Next I used the windows troubleshooter gui option to troubleshoot the specific network adapter. Troubleshooter said it could not identify the problem.
- Next I made sure that everyone in the network had the ability to access and edit the network folder. When I went to check the settings I noticed it was disconnected. I remapped the folder on the host and then attempted to use net view again. Unfortunately, the system error 1231 occured.
- At some earlier point in the days before I tried uninstalling and reinstalling the network adapter. This did nothing but I had to reset the network settings before attempting again. This also did nothing.
- I tried the following instructions from a reddit post
Open the Network Connections folder. Right click the local area network connection and click Properties. Double click Internet Protocol (TCP/IP). Click Advanced. Click WINS. Click the Enable NetBIOS Over TCP/IP button. This did not fix the problem.
Could the problem be a mismatch in the windows PE image and the windows 10 pro OS on the server? How could I tell? This forum post seems like it might be relevant but I don't really understand what they are talking about. I hope someone smarter than me can help.
