Dial Up - Dial IN Networking Service - trouble shooting - VPN as alternative/best option
There are hundreds of pages devoted to DUN connections and setup, however, I have attempted to remove spurious info and shorten things to what you need to focus on when using DUN as a *DIAL IN - DIAL OUT* service for your local network.
How to Connect to a Remote Server Using Dial-Up Networking
Microsoft /kb/145843
139710 - How to Enable Dial-Up Networking Server Capabilities
137820 - Microsoft Plus! Readme.txt File Contents (2 of 2) provides some issue fixes
Troubleshooting DUN
Hmm, so you went through the complete DUN server setup on 98SE with actual other computer name, having shared folders, etc.. did you properly setup the other server/client [XP, etc.]?
What server type did you indicate? TCP/IP [or IPX/SPX if you are still using that] must be used for network access.
Did you try scripting [which allows use of DUN and VPN] and/or VPN? Scripting would allow a DUN connection then institute VPN or other needed aspects.
Do you have an actual Windows Logon name and password or do you bypass logon? IF you bypass Windows logon your connection will likely fail. For full access use Microsoft Network Logon rather than Windows Logon.
Did you enable File and Printer sharing and set that up properly? Just like any network, you MUST share files and folders.
Did you set *share-level access* in Control Panel > Network > Access Control? *User-level access* requires a server {like PWS, IIS, Apache, or NT/XP/2000/2003/up, or some other application} to handle that access.
Did you check your firewall for port configuration? Yes, your firewall MUST be configured to allow the ports necessary for Windows Networking and/or VPN, because you ARE using TCP/IP.
GENERAL WINDOWS NETWORKING DIAGNOSTICS AND SETUP
DUN SERVER SETUP: IS THIS WHAT YOU DID?
Selected the Server Types tab and checked the following options: Log on to
network, Enable software compression, Require encrypted password, Require
data encryption and TCP/IP. Now click the TCP/IP Settings button.
Check Server assigned IP address and Server assigned name server addresses.
Click OK.
This setup is somewhat more difficult as it requires interaction and responses from various servers/services, encrypted password authentication, etc.. A failure at any stage denies connection.
You MUST know the exact [static] IP addresses [names generally fail], must pass and verify the exact passwords and user names, and shared resource addressings [\\yourcomp\sharedfolder\].
ALTERNATIVELY:
Click on the Server Type... button (or tab).
Select PPP: Windows 95, Windows NT 3.5, Internet from the "Type of Dial-Up
Server" pop-up list.
Turn off all of the listed options other than TCP/IP.
Click the TCP/IP Settings button at the bottom of this window.
Click Server assigned IP address on the top.
Click Specify name server addresses in the middle of the window. The section
below it should become active.
Enter the DNS number for the XP machine, OR, for your installed DNS application, OR, for your local machine with a HOSTS file containing local network entries.
Leave 0.0.0.0 in the two WINS fields.
Click OK in all the open windows to save the settings.
Click to create a shortcut, which will say it can't create one here, choose Desktop for the shortcut.
Then close out of Dial-up Networking.
Check the shortcut settings.
Did you or do you have these issues:
The first link page includes a few fixes which
might be related to your issue(s).
http://ludit.kuleuven.be/internet/kotnet/savepasw.html
Error message, "The computer you have dialed in to has denied
access because the username and/or password is invalid on the domain."
Microsoft /kb/148899/
VPN as a better connection type
To run VPN you MUST have the proper files installed within the system, and become familar with the various VPN requirements.
In 98FE/98SE/ME you MUST have installed the updated DUN service [version 1.3 or 1.4 respectively], installed and configured the VPN adapter in Network.
VPN allows much more control and access within the network, for instance, you want to be able to access multiple computers via your local network.
If you intend this extended type of connection [direct local network connection] then you should really use VPN.
Microsoft supplied some local Help files, look at:
C:\WINDOWS\HELP\VPN.CHM,
C:\WINDOWS\HELP\DIALER.CHM,
C:\WINDOWS\HELP\WINDOWS.CHM,
C:\WINDOWS\HELP\RNAAPP.CHM,
and C:\WINDOWS\HELP\NETWORK.CHM.
It can be a bit more difficult to setup, but it will supply a higher level of security and access. Here's some help:
Technet blog - Which ports to unblock for vpn traffic to pass through in firewall
Technet bb531150 - IPsec
Microsoft - /kb/325034 - troubleshoot VPN
Technet - bb545442 - Virtual Private Networks
Search Technet - L2TP/IPsec update - supplies links to various L2tp/IPsec information
PDF from umassd.edu - vpnforwin98_me.pdf - a good general reference
Microsoft supplied a 2002 updated VPN L2TP/IPsec for 98/98SE/ME/NT/2000 [95 is not supported/included]:
Microsoft - /kb/324915
Download Microsoft /win98/Install/1.0/W9XNT4Me/EN-US/msl2tp.exe
be cautious with this one... Take note of potential issues and requirements.