: Friday, December 28, 2001 4:05 PM
To: Exchange Discussions
Subject: RE: Client Access
That's what I originally thought. That's something hard
coded into the registry and I don't know of too many apps
that overwrite manual changes to the registry...
D
Overconfidence: Before you
://www.peregrine.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 4:13 PM
To: Exchange Discussions
Subject: RE: Client Access
Maybe so.. But what if you upgrade from 5.0 to 5.5 SP4?
Which...by the way, is what seems
Thanks for your help, I'm not an exchange guru (havn't been doing it for
long) and learned a lot.
I didn't need to make the ports static (wide open firewall).
I will push to remove this type of access.
it wasn't permissions (i thought it may have been this because a few weeks
ago I removed an
How many times are you going to send this Changing the subject line
will not garner different responses...
D
Hazards: There is an Island of Opportunity in the middle of every
difficulty, miss that, though, and you're pretty much doomed. -
http://www.despair.com
-Original Message-
For the love of god Stop sending the same friggin message with a
different subject!
D
Those who deny freedom to others deserve it not for themselves. -Abraham
Lincoln
-Original Message-
From: Ed Premus [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 9:26 AM
To:
LOL
After seeing the fourth post, I just knew steam was starting to come out of
your ears!
Paul Chinnery
Network Administrator
Mem Med Ctr
-Original Message-
From: Don Ely [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 1:54 PM
To: Exchange Discussions
Subject: RE: Client
Can you ping it by NAME or by IP Address?
-- Drew
Visit http://www.drewncapris.net! Go! Go there now!
This world in arms is not spending money alone. It is spending the sweat of its
laborers, the genius of its scientists, the hopes of its children. This is not
]]
Sent: Friday, December 28, 2001 11:01 AM
To: Exchange Discussions
Subject: RE: Client Access Problem
LOL
After seeing the fourth post, I just knew steam was starting to come out of
your ears!
Paul Chinnery
Network Administrator
Mem Med Ctr
-Original Message-
From: Don Ely [mailto:[EMAIL
why U no answer me!?!
===
Amit the CyBer DooD
===
-Original Message-
From: Don Ely [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 10:54 AM
To: Exchange Discussions
Subject: RE: Client Access Problem
For the love of god Stop sending
Don,
sorry about the multiples. I didn't think they were getting posted. So I
tried an number of different ways. I actually was going to email just you
and ask if this list was updated real time.
I know it is unsecure, but that is really not my choice, I have just
really locked this machine down
Premus [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 11:16 AM
To: Exchange Discussions
Subject: RE: Client Access
Don,
sorry about the multiples. I didn't think they were getting posted. So I
tried an number of different ways. I actually was going to email just you
and ask if this list
The pix has been in place around a year. I wasn't kidding when I said I
was going to email you and ask, so I wasn't being a smart A**.
_
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives:
of
skill by doubling your efforts, there's no end to what you can't do. - -
http://www.despair.com
-Original Message-
From: Ed Premus [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 11:24 AM
To: Exchange Discussions
Subject: RE: Client Access
The pix has been in place around a year
The reason you can no longer do this is because you have not set your static
RPC ports for the exchange server. This must have been done on the older
version and now that you have upgraded you will have to re-do it.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
of
skill by doubling your efforts, there's no end to what you can't do. - -
http://www.despair.com
-Original Message-
From: Ed Premus [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 11:24 AM
To: Exchange Discussions
Subject: RE: Client Access
The pix has been in place around a year
Discussions
Subject: RE: Client Access
The reason you can no longer do this is because you have not set your static
RPC ports for the exchange server. This must have been done on the older
version and now that you have upgraded you will have to re-do it.
-Original Message-
From: [EMAIL
Discussions
Subject: RE: Client Access
I agree with this. This is a bad idea to open up this communication via the
internet. A better solution would be to implement a VPN solution using PPTP
directly to the server or another RAS Server. I'm not aware of any problems
running RAS on the Exchange
?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 1:35 PM
To: Exchange Discussions
Subject: RE: Client Access
I agree with this. This is a bad idea to open up this communication via the
internet. A better solution would be to implement a VPN
Yes and it is wide open, any to any (it won't stay this way).
I havn't had it explained to me with viable content, but our company does
alot of work for other companies with secure networks. These networks
generally are not going to allow the vpn ports to be opened on their
network. However, we
Discussions
Subject: RE: Client Access
Since those static mappings are done in the registry, what upgrade could
have changed that?
D
Saving the world from Brick Level Backups and PST's - Ed Crowley
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday
should be downloading all of your updates, patches, etc... from another
system then applying them to the exchange server.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 1:39 PM
To: Exchange Discussions
Subject: RE: Client Access
I
To: Exchange Discussions
Subject: RE: Client Access
Since those static mappings are done in the registry, what upgrade could
have changed that?
D
Saving the world from Brick Level Backups and PST's - Ed Crowley
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday
Sorry for not being clear,
upgraded to 5.5 sp4
patched IIS
updated ie to 5.5 sp2 and security patches
This is kind of a weird situation, security was not a concern of this
company until around the last six months. I do want to close the machine
off from the internet as much as possible, but I
What are you using in your attempt to connect to the Exchange server over
the Internet?
-Original Message-
From: Ed Premus [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 1:49 PM
To: Exchange Discussions
Subject: RE: Client Access
Sorry for not being clear,
upgraded to 5.5
Don't access the internet from it, I have no good explanation for why I
upgraded the browser.
_
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To
based client.
I believe the FAQ has some information on doing this.
-Original Message-
From: Ed Premus [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 1:49 PM
To: Exchange Discussions
Subject: RE: Client Access
Sorry for not being clear,
upgraded to 5.5 sp4
patched IIS
updated
for something. -- Henry David Thoreau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, December 28, 2001 1:42 PM
To: Exchange Discussions
Subject: RE: Client Access
Either way... Double check the Registry settings for the RPC ports
Oulook 2000 SP2
_
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL
using a Mapi based client.
I believe the FAQ has some information on doing this.
-Original Message-
From: Ed Premus [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 1:49 PM
To: Exchange Discussions
Subject: RE: Client Access
Sorry for not being clear,
upgraded to 5.5 sp4
I suppose. If you accessing OWA from the Exchange Server I guess this would
be relevant.
-Original Message-
From: Drewski [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 1:51 PM
To: Exchange Discussions
Subject: RE: Client Access
Well, for OWA to work with the current
-Original Message-
From: Ed Premus [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 2:49 PM
To: Exchange Discussions
Subject: RE: Client Access
Sorry for not being clear,
upgraded to 5.5 sp4
patched IIS
updated ie to 5.5 sp2 and security patches
This is kind
-Original Message-
From: Don Ely [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 2:47 PM
To: Exchange Discussions
Subject: RE: Client Access
Oh, there you go. SP4 would have changed things back the
WAY they SHOULD be.
D
Who's General Failure and why's he reading my
-
From: Roger Seielstad [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 2:55 PM
To: Exchange Discussions
Subject: RE: Client Access
I've done plenty of SP upgrades on Exchange and can unequivicably state that
it does NOT remove the static port mappings
PROTECTED]]
Sent: Friday, December 28, 2001 3:58 PM
To: Exchange Discussions
Subject: RE: Client Access
SP Upgrades or Exchange upgrades. I believe he stated that he upgraded to
Exch 5.5 then SP4. The Exchange upgrade would have reset the RPC
portsI think. Not to mention, anytime you upgrade
-Original Message-
From: Roger Seielstad [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 12:55 PM
To: Exchange Discussions
Subject: RE: Client Access
I've done plenty of SP upgrades on Exchange and can unequivicably state that
it does NOT remove the static port mappings
-Original Message-
From: Roger Seielstad [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 12:55 PM
To: Exchange Discussions
Subject: RE: Client Access
I've done plenty of SP upgrades on Exchange and can unequivicably state that
it does NOT remove the static port mappings
who has nowhere to land
but in the ocean of reality. - - http://www.despair.com
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 1:13 PM
To: Exchange Discussions
Subject: RE: Client Access
Maybe so.. But what if you upgrade from 5.0
was upgrading from an earlier
version. This would fit the problem he was having.
-Original Message-
From: Don Ely [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 3:13 PM
To: Exchange Discussions
Subject: RE: Client Access
Where did you see that he upgraded from 5.0 to 5.5 SP4?I don't
Upgraded from 5.5 SP3
I checked for the static RPC ports and the dword entries for tcp/ip port
are not there. This is the info I got from the knowledge base. Is this
correct?
Also I can't remember where but isn't there somewhere on the information
store besides the recipients container, that
Also we are about to upgrade from 5.5 standard to enterprise, are there
any pitfalls that I need to know about?
_
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives:
Sorry to keep posting.
I just tried to logon to the machine as the local administrator, dialed
up, started the vpn, and tried to set up my profile logged on as the local
administrator. When the logon pop up came up, which I had used previously,
I entered my information. It failed, it is like it
Somebody is seriously full of )#($
-Original Message-
From: Ed Premus [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 5:44 PM
To: Exchange Discussions
Subject: RE: Client Access
Upgraded from 5.5 SP3
I checked for the static RPC ports and the dword entries for tcp/ip port
You are correct, they are not there. That is because by default it is
dynamic. The registry entries force it to be static.
-Original Message-
From: Ed Premus [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 3:44 PM
To: Exchange Discussions
Subject: RE: Client Access
Upgraded
43 matches
Mail list logo
