I thought you could only press Escape in Windows 95. I stand corrected. Robin.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 25 October 2001 13:25 To: MS-Exchange Admin Issues Subject: RE: Remote connectivity problem Using the Outlook client. also Win98 -Michèle Immigration site: <http://LadySun1969.tripod.com> Our new 2001 Miata: <http://members.cardomain.com/bpituley> Tiggercam: <http://www.tiggercam.co.uk> --------------------------------------------------------- Plan to be spontaneous tomorrow. --------------------------------------------------------- -----Original Message----- From: Robin Lawrie [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 25, 2001 8:23 AM To: MS-Exchange Admin Issues Subject: RE: Remote connectivity problem Using the Outlook client. Aah, this is Windows 95 isn't it. I'm assuming the users home PC's were Windows NT/2000.........wrong assumption! Robin. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 25 October 2001 13:18 To: MS-Exchange Admin Issues Subject: RE: Remote connectivity problem Using the Outlook client. Here it is! Q182158 "NOTE: When you start Windows, do not press ESCAPE when prompted for the Windows password, or you will not be able to access the .ost file because the proper credential information has not been supplied." -Michèle Immigration site: <http://LadySun1969.tripod.com> Our new 2001 Miata: <http://members.cardomain.com/bpituley> Tiggercam: <http://www.tiggercam.co.uk> --------------------------------------------------------- "Pinky, are you pondering what I'm pondering?" "I think so, Brain, but where are we going to find a duck and a hose at this hour?" --------------------------------------------------------- -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 25, 2001 8:08 AM To: MS-Exchange Admin Issues Subject: RE: Remote connectivity problem Using the Outlook client. It was my understanding that that was not enough. They must also log into the machine itself with the network credentials -- even if they let it "time out" as start up. There's a Q article about this somewhere.... -Michèle Immigration site: <http://LadySun1969.tripod.com> Our new 2001 Miata: <http://members.cardomain.com/bpituley> Tiggercam: <http://www.tiggercam.co.uk> --------------------------------------------------------- I can bend minds with my spoon. --------------------------------------------------------- -----Original Message----- From: Robin Lawrie [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 25, 2001 3:30 AM To: MS-Exchange Admin Issues Subject: RE: Remote connectivity problem Using the Outlook client. Are the users home machines that they're logging in from on the domain or are they standalone machines? If they are on the domain, are the usernames and passwords that they log onto the machine with the same as their network username and password? If not, or if the machines are not on the domain, then it could be that when Outlook starts and tries to connect to the Exchange server, it is passing the credentials of the locally logged on user to Exchange. Exchange doesn't recognise these users and so doesn't allow a connection. What you need to do in Outlook is define what network logon credentials to use. In Outlook on the users home PC's, select Tools, Services. Select Microsoft Exchange Server, then click Properties and select the Advanced Tab. Where you get the drop down box for Network Logon Credentials, select None and ok everything. Now, when you start up Outlook, you will be prompted for your username, password and domain. Enter your network details and you should get in. Robin. -----Original Message----- From: Patrick Rouse [mailto:[EMAIL PROTECTED]] Sent: 24 October 2001 19:44 To: MS-Exchange Admin Issues Subject: Re: Remote connectivity problem Using the Outlook client. William, this leads me to believe he is not using VPN, but allowing people to logon remotely from the Public Internet. Very bad!!!!!! Note: Our firewall is not blocking port 135 and there is not a problem > connecting to our 5.5 server using the Outlook client remotely. > This is a multi-part message in MIME format. > > ------_=_NextPart_001_01C15CA9.61402952 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > I am in the process of migrating our dept from NT 4 To W2k and from Ex > 5.5 to E2k. > =20 > We are having a problem connecting to our E2K server using the Outlook > client remotely from outside our organization. > I have many users (incl myself) that connect to the Exchange server from > other Subnets/Domains and home using their BB provider. > =20 > When trying to make a connection to the E2K server from home I receive > the following message Your Microsoft Exchange Server is unavailable." > It gives me the options of 'work offline', 'retry', and 'cancel'=20 > =20 > Making the connection to our E2K server from a different subnet or > Domain in the organization works and I have no problems using the > Outlook client remotely > =20 > Now while this is not a problem with our Exchange 5.5 server it is with > our E2K server. This is leading me to believe that there is a policy > setup by default (because I have not defined any security policies at > this time). Are there default security policies set up during install > that prohibit access from undefined networks? > =20 > While trying to connect I Used netstat to watch some of the > communication and noticed that both 5.5 and E2K start the communication > with a sync packet sent on port 135. > Note: Our firewall is not blocking port 135 and there is not a problem > connecting to our 5.5 server using the Outlook client remotely. > Any suggestions? > TIA > AlV > Albert Vasquez > MicroComputer Support Service Group > Lucy Stone Hall > Room 323 > 732-445-6950 x21=20 > > =20 > > ------_=_NextPart_001_01C15CA9.61402952 > Content-Type: text/html; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > <HTML><HEAD> > <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = > charset=3Diso-8859-1"> > > > <META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR></HEAD> > <BODY> > <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN = > class=3D284595915-24102001>I am=20 > in the process of migrating our dept from NT 4 To W2k and from Ex 5.5 to = > > E2k.</SPAN></FONT></DIV> > <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20 > class=3D284595915-24102001></SPAN></FONT> </DIV> > <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN = > class=3D284595915-24102001>We are=20 > having a problem connecting to our E2K server using the Outlook client = > remotely=20 > from outside our organization.</SPAN></FONT></DIV> > <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN = > class=3D284595915-24102001>I have=20 > many users (incl myself) that connect to the Exchange server from=20 > other Subnets/Domains and home using their BB = > provider.</SPAN></FONT></DIV> > <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20 > class=3D284595915-24102001></SPAN></FONT> </DIV> > <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN = > class=3D284595915-24102001>When=20 > trying to make a connection to the E2K server from home I receive the = > following=20 > message Your Microsoft Exchange Server is unavailable." It gives = > me the=20 > options of 'work offline', 'retry', and 'cancel' </SPAN></FONT></DIV> > <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20 > class=3D284595915-24102001></SPAN></FONT> </DIV> > <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN = > class=3D284595915-24102001>Making=20 > the connection to our E2K server from a different subnet or Domain in = > the=20 > organization works and I have no problems using the Outlook client=20 > remotely</SPAN></FONT></DIV> > <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20 > class=3D284595915-24102001></SPAN></FONT> </DIV> > <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20 > class=3D284595915-24102001>Now while this is not a problem with our = > Exchange=20 > 5.5 server it is with our E2K server. This is leading me to believe that = > there=20 > is a policy setup by default (because I have not defined any security = > policies=20 > at this time). Are there default security policies set up during install = > that=20 > prohibit access from undefined networks?</SPAN></FONT></DIV> > <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20 > class=3D284595915-24102001></SPAN></FONT> </DIV> > <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN = > class=3D284595915-24102001>While=20 > trying to connect I Used netstat to watch some of the communication and = > noticed=20 > that both 5.5 and E2K start the communication with a sync packet sent on = > port=20 > 135.</SPAN></FONT></DIV> > <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN = > class=3D284595915-24102001>Note:=20 > Our firewall is not blocking port 135 and there is not a problem = > connecting to=20 > our 5.5 server using the Outlook client remotely.</SPAN></FONT></DIV> > <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN = > class=3D284595915-24102001>Any=20 > suggestions?</SPAN></FONT></DIV> > <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20 > class=3D284595915-24102001>TIA</SPAN></FONT></DIV> > <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20 > class=3D284595915-24102001>AlV</SPAN></FONT></DIV> > <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN = > class=3D284595915-24102001> > <P><FONT size=3D2>Albert Vasquez<BR>MicroComputer Support Service = > Group<BR>Lucy=20 > Stone Hall<BR>Room 323<BR>732-445-6950 x21 = > </FONT></P></SPAN></FONT></DIV> > <DIV> </DIV> List Charter and FAQ at:<BR> http://www.sunbelt-software.com/exchange_list_charter.htm<BR> List Charter and FAQ at:<BR> http://www.sunbelt-software.com/exchange_list_charter.htm<BR> List Charter and FAQ at:<BR> http://www.sunbelt-software.com/exchange_list_charter.htm<BR> List Charter and FAQ at:<BR> http://www.sunbelt-software.com/exchange_list_charter.htm<BR> List Charter and FAQ at:<BR> http://www.sunbelt-software.com/exchange_list_charter.htm<BR> List Charter and FAQ at:<BR> http://www.sunbelt-software.com/exchange_list_charter.htm<BR> List Charter and FAQ at:<BR> http://www.sunbelt-software.com/exchange_list_charter.htm<BR> </BODY></HTML> > > ------_=_NextPart_001_01C15CA9.61402952--
