Conference chefs::ms-exchange

I'm sure you're aware this is not the place to report
this problem (& now I'll chase over to INTERNET_TOOLS to
respond there, also).

The tunnel webpages and readme file which comes with
the keys do make it clear how to get support.
Please call your local helpdesk or check the tunnel
FAQ page ( http://www.imc.das.dec.com/imcdocs/tunfaq.html).

My WAG is that you have an Ethernet adapter also in your
computer - the FAQ page (and the subscription pages, also)
has a discussion and pointer to a fix for this problem.

    
    	I was not able to cross post to INTERNET_TOOLS. I kept getting
    	booted when I tried to write to the conference. In any event
    	I tried the help desk route. They were not able to help
    	with either problem. I am now able to connect to exchange
    	again after deleteting EVERY network related bit in the
    	configuration and reinstalling and reconfiguring.
    
    	As far as the tunnel goes: I spent almost 4 hours with
    	the helpdesk after installing the ISDN update as requested.
    	They claim that everthing is configured properly and I
    	still can't connect. The help desk said that some one
    	would get back to me. This was early monday afternoon.
    	It's now Wednesday afternoon and I'm still waiting for
    	a call back. SIGH!
    
    	Ken
    

RE: .0

The following are all of the parameters that I have set on my system, which
is currently working fine using the tunnel with AT&T as my ISP.  Some of
these settings were found by trial and error, but they have been working
without any changes for at least 6 months.

As far as the suggestion in .1, I only run with *either* the modem *or* the
Ethernet card in the system, never both, and I re-boot when I switch between
them.  It works for me with no requirements for different configurations.
I just simply shutdown the system (power off), remove the old card, put in
the new card, and power on.

Anyway, here are the parameters.

Start->Control Panel->Networks->Configuration shows these entries:
	Primary Network Login is Microsoft Network
	Client for Microsoft Networks
	    Logon to NT Domain, domain Digital1
	    Quick logon
	DEC Pseudo Network Driver for Internet Tunnel
	    Driver Type is Enhanced Mode (32-bit)
	    Bindings are TCP/IP->DEC Pseudo Network Driver for Internet Tunnel
	    Advanced is IP Address for tunnel is same as gateway address
	TCP/IP Pseudo Network Driver for Internet Tunnel
	    IP Address is obtained automatically
	    WINS configuration is Enable WINS resolution, with DHCP off,
		and addresses 16.126.32.167 and 16.52.48.57
	    Gateway is blank
	    Bindings are Client for Microsoft Network
	    Advanced is blank
	    DNS Configuration is Enable DNS, host Moreauk1, domain Digital1,
		DNS Server Search order 204.127.129.1
					204.127.160.1
					16.135.96.45
		Dommain Suffix search order alf.dec.com
					ogo.dec.com
					lac.dec.com
					pko.dec.com

My Computer->Dial-up Networking->AT&T Worldnet->(right-click)->Properties->
Server Type shows
	Type of Dialup Server: PPP, Win95, WinNT, Internet
	Logon to network is checked
	Enable software compression is checked
	Require encrypted password is not checked
	Allowed network protocols, only TCP/IP is checked
	TCP/IP settings shows
	    Server assigned IP address is checked
	    Specify Name Server address is checked
	    Primary DNS is 204.127.129.1
	    Secondary DNS is 16.135.96.45
	    Primary WINS is 16.126.32.167
	    Secondary WINS is 16.20.32.12
	    Use IP header compression is checked
	    Use default gateway on remote network is checked
	
Good luck.

-- Ken Moreau
   who feels obligated to help someone who has such a fine first name :-)

	Ken:

	Thanx for the information but I fianlly received a call back
	from the helpdesk on thursday afternoon. After checking a
	few things it was determined that the problem was due to
	the fact that I was using the Worldnet Dialer and not the
	Windows 95 Dialer. A call to Worldnet support determined
	that I was using one of the earliest releases of the
	worldnet client available and could not modify it to
	use the other dialer. I downloaded the latest client
	for Windows95 and I connected on my first attempt.


	This doesn't explain the problems that I had with exchange,
	but at least I'm able to connect both ways now.


	Ken