David locates a possible solution
When we last left David, he had recently acquired cable modem service in his home. He was interested in using this service to access his office’s network via VPN. However, after setting everything up on his home PC, he was unable to gain successful access to the company network.
What dumbfounded David was the fact that he was able to access the network on his laptop via his dial-up access using VPN. He couldn’t figure out why his cable modem, a faster ISP, would not allow him to gain full access. Undaunted, he searched for solutions on the Microsoft Knowledge Base and other sources on the Internet. After a diligent search of the Microsoft Knowledge Base one evening, he finally struck gold. It seemed that Microsoft had a solution to his problem posted within the database, and he had accidentally passed it up on his previous searches.
A simple solution, or so it seems
The answer, it seemed, was a simple one. The Knowledge Base article gave David easy-to-follow instructions on how to set up the properties of his Windows 98 SE network. He was first instructed to go into the Control Panel and open up the Network icon. From there, he was told to highlight the Client For Microsoft Networks, located in the list of clients and protocols for the network on his home PC. Once he did so, he clicked on properties and watched as the Client For Microsoft Networks Properties window appeared. After reading the article a bit more, he placed a check next to Log On To Windows NT Domain, as instructed, and entered the Windows NT domain of his company’s network in the blank provided him. He clicked OK on both the properties window and the network window, and was told to reboot his machine.
His problems weren’t over yet, however. On reboot, David received an error stating that a domain couldn’t be located. He clicked OK and another window popped up requesting his user name, domain name, and password. He entered his work user ID and password, along with the domain he was attempting to connect to, then clicked OK. Once again, he was confronted with another error stating that the domain could not be found. He clicked OK once more, and let Windows 98 SE load as it normally would.
On a hunch, David opened the VPN access to his company’s network and dialed in as he had done many times before on his company laptop. As a test, he opened up his Internet Explorer and typed in the location of a server on the network. After a few seconds, he had full access to all folders on the network in which he had permissions. Only this time, he was able to access all the files much faster, thanks to the cable modem.
Have you had an experience similar to that of David’s? Have you tried unsuccessfully to access your company’s network using high-speed access? If so, we want to hear your stories! Feel free to post a message below or send us a note.