General discussion

  • Creator
    Topic
  • #2081945

    Windows NT Remote User Problem

    Locked

    by rc3cds ·

    My place of employment has windows NT 4.0 installed with service pack 5 installed. My remote users which use 95 and 98 are able to connect to the server but not able to browse the network. “No domain server availiable” is part of the error I get.All protocals are set up correctly, the server has all correct specs setup, what could possiably be the problem. (Remember- they can get into the server with no problem, but once in they simply can’t find any resources on the network).

All Comments

  • Author
    Replies
    • #3900062

      Windows NT Remote User Problem

      by csheltcomp ·

      In reply to Windows NT Remote User Problem

      Have you tried to reinstall SP5. Sometimes that will fix certain glitches. Also make sure that you have the correct Domain set up on the remote systems as well as unique computer names for each one. Try to ping the servers.

    • #3900061

      Windows NT Remote User Problem

      by veetel ·

      In reply to Windows NT Remote User Problem

      Copy your hosts and lmhosts files into the C:\WINDOWS directory of the remote users PCs. That should take care of it.

    • #3900059

      Windows NT Remote User Problem

      by phigginson ·

      In reply to Windows NT Remote User Problem

      Hi,

      If you work with RAS, the good solution, add WINS server into your Domain.
      Setup all client to client to connect to this WINS (VIA Network properties)

      It’s better solution.

      Bye

    • #3900058

      Windows NT Remote User Problem

      by mark_lt ·

      In reply to Windows NT Remote User Problem

      Ensure that the wins entries are included in the DHCP setup

    • #3900055

      Windows NT Remote User Problem

      by mcse lee ·

      In reply to Windows NT Remote User Problem

      I agree with #3 and #4 – add a WINS Server to the network, and make sure that your dialup users are configured to use it. This has solved multiple problems for me (in addition to the one you described). If resources are tight, you could also use local LMHOSTS files on the remote PC’s, but this has the disadvantage of increased administration to keep them synchronized every time you make a significant change to the network – if the network is fairly static, and won’t change for a long while, then this may be an option.

    • #3900054

      Windows NT Remote User Problem

      by eshar ·

      In reply to Windows NT Remote User Problem

      on your clients pc go to my computer right click on dial up click on the properties tab click on server type make sure u lan protocol is only running for eg tcpip. click on proerties of tcip ip then manualy add the d/g s/m and Dns accept this. Then check if ur network works with dhcp.

    • #3900030

      Windows NT Remote User Problem

      by peterb ·

      In reply to Windows NT Remote User Problem

      On the Win95/98 machines, have you added the hosts into LMHOSTS file? Make sure you purge the entry if you don’t wish to restart the machines.
      Make sure the LMHOSTS has no extension, and once added, goto a command prompt and type: nbtstat -R

    • #3900011

      Windows NT Remote User Problem

      by lewerke ·

      In reply to Windows NT Remote User Problem

      This problem is actually addressed directly by MS article Q145593. If you can connect, but can’t use ping, net use, or net view commands to connect to remote computers, it is probably because the workstation name is already registered on the LAN. This causes the workstation service (and NETBIOS functions) to not initialize. To solve this, change the workstation name before you dial-in via RAS to a name that is not being used on the LAN.

    • #3903169

      Windows NT Remote User Problem

      by rotocron ·

      In reply to Windows NT Remote User Problem

      2 Things to check:

      1) Make sure the “TCP/IP Routing” is enabled in ‘network/properties/protocols/tcp-ip’.

      2) Make sure the RAS clients are enabled to talk to the “Entire Network” and not just “This Machine” in RAS properties.

    • #3740345

      Windows NT Remote User Problem

      by rc3cds ·

      In reply to Windows NT Remote User Problem

      This question was auto closed due to inactivity

Viewing 9 reply threads