![]() ![]() You can also use a LMHOSTS file, and optionally statically map the MAC address.īoth help, when (its likely) some parts of the total local networking stack arent "right". Neither of above is strictly necessary, but they make life a lot easier. it may make sense to use a hosts file with static ip addresses If you cannot connect from one PC to another, you probable cannot connect to the VM2 either. When you can connect from PC1 to PC2 and vice versa, you can also connect to the HAAS VM2. I will be back in about 3 hours.įor troubleshooting purposes, test with shares from one PC to another. I´m in Barcelona, Spain, and its now 7:50 am. If you cant get it to work, I can try to help with a remote network connection (teamviewer etc) if you want. The same affects network printers, scanners, shares globally. The whole local networking things is horrendously crippled - because MS in their total lack of wisdom changed a lot of stuff from how its been working for over 15 years. ![]() Its also useful to make a share on the network, to which the VM2 can connect. The user:uname is optional and may not be needed. Use the older (dates back to lanman days, in 199x or so) command prompt syntax. You can do this from a command prompt - and unless it works from a command prompt no way will it work graphically. You will probably need a user on the local machine- ie the username of the VM2. Its not necessary for it to show up in the network, for the network hard drive mapping to work. The issue is mostly with Windows 7- that has crap and different local network sharing (they changed lots of things for no good reasons. Any help on how to resolve this would be much appreciated! It seems to be somewhat of a known issue with Windows 7 as you can find quite a few people online who have had similar problems with the setup. We also tried the HAAS/ABCDE user/pass combination but it also did not help. Search for "Network security: LAN Manager authentication level" double click it, select from pulldown menu "send LM & NTLM responses" So, netshare works, we can ping the machine (192.168.1.118), we can access the machine via web browser - BUT the VM2 simply won't show up in the Windows 7 network (on any of our workstations) and thus we can't map the harddrive of the VM2.Ħ. However, getting the VM2 to show up in the Windows 7 network is a totally different story. We let the machine automatically pull IP settings via DHCP and can setup the Netshare option just fine. The instructions seem very straightforward. ![]() I've been trying to get our VM2 setup in our network. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |