1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

No Domain Server Available

Discussion in 'Networking (Hardware & Software)' started by stever0114, 2002/05/16.

Thread Status:
Not open for further replies.
  1. 2002/05/16
    stever0114

    stever0114 Inactive Thread Starter

    Joined:
    2002/05/16
    Messages:
    3
    Likes Received:
    0
    I am connected via work VPN client through my cable internet connection. Was told that via this connection, I could not access any Novell servers. Was just set up via work laptop to connect to non-Novell server utilizing Windows 2000. I can connect to work LAN server via this connection at home and even with my old Windows 95 laptop, but not with my home desktop on Windows 95. I configured my desktop to match my old Windows 95 laptop under Control Panel/ Networking. Logon is set to logon to NT DOMAIN. Even with that once the VPN connection is established and it requests logon using Client for Microsoft Networks and I provide username and password, I get a NO DOMAIN SERVER WAS AVAILABLE TO VALIDATE YOUR PASSWORD. Both the old laptop and my desktop are OSR2. Found several articles in Microsoft Knowledge base on subject but no updates, except go to Windows 98. Don't think I should have to do that if I know it works on old laptop Windows 95. Any ideas or suggestions?
     
  2. 2002/05/17
    Hulka

    Hulka Inactive

    Joined:
    2002/01/07
    Messages:
    330
    Likes Received:
    0
    Try these little tips....
    • If you're getting prompted for a Windows password upon system startup, press Esc at the first logon screen to prevent network logon or a Windows-validated session. This allows domain logon through Dial-Up Networking.
    • The computer name must be unique and Workgroup name should be the same as the domain to which you are trying to connect.
    • Make sure TCP/IP and PPTP are bound to Client for Microsoft Networks, the Dial-Up Networking adapter and the VPN adapter (can't remember what it is called exactly on a Win9x box)
    • If you're using static IP information for the VPN connection (not getting WINS, DNS and IP address via DHCP), make sure you have a WINS server address configured.
     
    Last edited: 2002/05/17

  3. to hide this advert.

  4. 2002/05/17
    stever0114

    stever0114 Inactive Thread Starter

    Joined:
    2002/05/16
    Messages:
    3
    Likes Received:
    0
    Thanks. I'll give your suggestions a shot.
     
  5. 2002/05/20
    stever0114

    stever0114 Inactive Thread Starter

    Joined:
    2002/05/16
    Messages:
    3
    Likes Received:
    0
    Unfortunately, the suggested tips did not work either. I checked to make sure the suggested functions were bound to Client for Microsoft Networks, which they were. I hit <ESC> when getting the initial Microsoft Networking signon. Then after doing the initial connection via VPN processes, got the pop up box again, with the Domain filled in. I had to type in the User Name and Password. Got the NO DOMAIN TO VERIFY PASSWORD message as before. Also verified that the domain was set up as the Workgroup and NT Domain under the signon. In the previous message I failed to mention I was on DUN 1.3 and Winsock 2. I upgraded to DUN 1.4 but that didn't help either.
     
  6. 2002/05/20
    unixfan

    unixfan Inactive

    Joined:
    2002/01/26
    Messages:
    282
    Likes Received:
    0
    On the working install, are you using a WINS server or LMHOSTS file? Try disabling third-party software (firewall, anti-virus, etc.) in case they are conflicting. Can you ping any remote servers after making the VPN connection? Are you getting a valid IP address?
     
    Last edited: 2002/05/20
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.