Ben,
Try this for size. At one company I used to work for they had a WINS
failure and had to reregister everything in WINS. In order to "be
proactive" for any future WINS failures, they put static entries for all NT
servers in DNS (about 350+ servers). Oh, I forgot to mention that as a
second precautionary measure, they also created static WINS entries for all
NT servers as well. They thought that importing the static WINS entries was
a very rapid way of recovery. How do you like that? What a nightmare! I
hear that they have a lot of NETLOGON problems these days.
S.
"I see stupid people...
...they're everywhere...
they walk around like everyone else
...they don't even know that they're dumb."
-----Original Message-----
From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 5:07 PM
To: Exchange Discussions
Subject: RE: E2K Windows-98 VPN Connection Problem
Static mappings in WINS should really only be used for non-Windows based
servers (i.e. Unix-based) that for some reason, you need to resolve to their
netbios names. I'm not arguing that WINS is bad or that you shouldn't use
it, but for goodness sakes, don't put static WINS mappings in for
Windows-based computers. You're just asking for problems. What are you
going to do if you ever have to change the IP of some of the servers that
have static mappings? Guess what, you just introduced some corruption into
your WINS database. BELIEVE me, we have been dealing with crap like this
for a while as a result of past mistakes. I haven't been deeply involved,
but those that are doing the cleanup have said that it is a nightmare.
Spare yourself while you still can. I am sure there have got to be some Q
articles that detail why you don't use static mappings (except on Unix-based
systems), but I don't have the time right now to look them up. Maybe I will
another day.
Ben Winzenz, MCSE
Network/Systems Administrator
Peregrine Systems, Inc.
-----Original Message-----
From: Anthony L. Sollars [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 4:11 PM
To: Exchange Discussions
Subject: RE: E2K Windows-98 VPN Connection Problem
Actually just restarting wins allowed my VPN Outlook user to connect to
exchange where before when wins was stopped, they could not. Though my locl
Outlook users were not effected at all, so it must have something to do with
the VPN equation. Oh well it works great now, so I will leave wins in place.
Also, why are static WINS mappings so evil if their mapped for a statically
IP'd server. Just wondering, because I have never heard this, but I owuld
like to know why?
-TOny
-----Original Message-----
From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 12:46 PM
To: Exchange Discussions
Subject: RE: E2K Windows-98 VPN Connection Problem
Ugh, are you serious? Static mappings in WINS are EVIL. Besides, DNS is
where most of these problems are. Outlook uses DNS to resolve the Exchange
server, not WINS. If Outlook is slugglish, putting static entries in WINS
won't do anything to resolve the problem.
Ben Winzenz, MCSE
Network/Systems Administrator
Peregrine Systems, Inc.
-----Original Message-----
From: Anthony L. Sollars [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 2:47 PM
To: Exchange Discussions
Subject: RE: E2K Windows-98 VPN Connection Problem
Make sure you have WINS available for resolution and static mappings for
your mail servers. I no MS says win2k does not need wins but as many have
found out, that turining off wins causes many problems. I have directly
discovered problems with Outlook over VPN when not using the wins service.
-TOny
-----Original Message-----
From: McKnight, Charles [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 11:47 AM
To: Exchange Discussions
Subject: RE: E2K Windows-98 VPN Connection Problem
We had a similar deal on several 9x machines after moving to a new (5.5 in
our case) server and it was simply that the new exchange server didn't have
a DNS entry.. we added this and it immediately fixed it for all of these
machines so you might try looking into a DNS, hosts file solution.. but
again this was on and NT4/exch 5.5 setup so I may be way off..
Charles
Charles F. McKnight
PC/Lan Specialist
Mercy Health System - NWA
[EMAIL PROTECTED]
> -----Original Message-----
> From: Michael Marchiondo [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 06, 2001 1:35 PM
> To: Exchange Discussions
> Subject: E2K Windows-98 VPN Connection Problem
>
>
> Hello Folks,
>
> This one has me stumped and my next stop is PSS but I thought
> I would try
> here first.
>
> We have been running Exchange 5.5 in our Windows 2000 domain
> for quite some
> time with the ADC. When E2K SP1 was released we started planning our
> migration. We installed the E2K server in the same site and
> moved all the
> mailboxes to the new server. We setup our cc:Mail connector and SMTP
> connector on the new server and disabled the old ones.
>
> Despite a few bumps it is working fairly well. We have a
> mixture of Windows
> 2000, NT 4.0, 98, and one ME client all using Outlook 2000. Everybody
> connects fine on the LAN.
>
> Some clients connect to the LAN via a VPN connection. All
> Windows 2000
> clients connecting this way work fine. The Windows 98 and
> one ME client do
> not. When starting Outlook these clients just hang forever.
>
> When looking at the profile we see that the server name has been
> automatically switched as usual. However, if we rebuild the
> profile and try
> to resolve the mailbox name, that too hangs forever. If we
> create a mailbox
> on the Exchange 5.5 server and try to resolve that it all
> works fine. Any
> attempt to contact the Exchange 2000 server instead results
> in the process
> hanging - only on 98 and ME. Win2K works fine.
>
> We can map shares, ping, and do all kinds of other network
> things from these
> Windows-98 clients via VPN to the Exchange 2000 server. The
> connectivity
> seems to be there. We have tested with RPCPing and so on as
> well and that
> all works.
>
> I can't figure out what VPN would have to do with it and why
> it works fine
> for Windows 2000 clients. All work fine on the LAN. We have
> only seen this
> problem with VPN and only to the Exchange 2000 server - not
> the Exchange 5.5
> Server. We also tried installing the Active Directory client
> add-on for
> Windows 9x (DSCLIENT) and that didn't fix it either.
>
> Any thoughts?
>
> Thanks,
>
> Michael
>
> _________________________________________________________________
> 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 PROTECTED]
>
_________________________________________________________________
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 PROTECTED]
_________________________________________________________________
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 PROTECTED]
_________________________________________________________________
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 PROTECTED]
_________________________________________________________________
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 PROTECTED]
_________________________________________________________________
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 PROTECTED]
_________________________________________________________________
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 PROTECTED]
