Re: Netbios to Active Directory Name Resolution Question

From: Steven Halsey [MSFT] (Stevhal_at_Online.Microsoft.com)
Date: 06/28/04 

Date: Mon, 28 Jun 2004 10:58:14 -0700

I think that will fix it for you. The problem becoming that now you will
have to manage the static WINS mapping and if the Exchange server IP changes
then it becomes problematic to fix the WINS issue. Static WINS is
definitely not a recommended deployment, but in the situation you describe
it is probably what you need to do. 

-- 
Steven Halsey
Stevhal@online.microsoft.com
Microsoft Exchange
Please do not send email directly to this alias.  This alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Midnight Java Junkie" <jolly@joy.com> wrote in message 
news:eIEDc.21555$OT6.10096661@news4.srv.hcvlny.cv.net...
> Steven:
>
> It cannot be this simple.  Wins server, Static Mapping.  Netbios scope I
> guess would be the name that they see in terms of the workgroup on that
> side, I guess it really does not matter since its resolving IP addresses.
> So, hmm, lets have dinner when betty leaves (LHDWBL), if the DHCP server 
> on
> the business side is even set up to shell out the WINS server information,
> which I hope it is, then its as simple as telling the WINS server, "oh, by
> the way, if anybody asks you where EXHANGESERVER (NO, I did NOT use that
> name!) is, you can tell them its 192.168.1.99 which will solve the
> resolution problem.
>
> Jeeze, it CANNOT be THAT SIMPLE!
>
> Rog
>
>
>
> "Steven Halsey [MSFT]" <Stevhal@Online.Microsoft.com> wrote in message
> news:uohVzwEXEHA.128@TK2MSFTNGP10.phx.gbl...
>> So a couple of things that might help...
>>
>> What about delegating the Exchange DNS Zones out to the Exchange DNS on
> the
>> business DNS? Not sure if this fixes your issue but it would be closer to
>> expected operations, with Outlook 2003 FQDN can be used to resolve the
>> Exchange server. Since all the Business DNS would need to do was point
>> queries to the Exchange DNS as needed it should be minimal change.  I
> think
>> you mentioned you were using Outlook2000 client so this may not solve 
>> your
>> issue but I would recommend it anyways.
>>
>> What about creating static WINS records for the Exchange servers on the
>> business WINS?  This should allow clients on the business side to resolve
>> the name of the Exchange server on the business network.
>>
>> -- 
>> Steven Halsey
>> Stevhal@online.microsoft.com
>> Microsoft Exchange
>>
>> Please do not send email directly to this alias.  This alias is for
>> newsgroup purposes only.
>>
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>>
>>
>>
>> "Midnight Java Junkie" <jolly@joy.com> wrote in message
>> news:GgsDc.11835$OT6.7868452@news4.srv.hcvlny.cv.net...
>> > Dear Colleagues:
>> >
>> >
>> >
>> > First and foremost, thank you for your time.
>> >
>> >
>> >
>> > I was hired by a client to set up an Exchange 2000 server and its
>> mailboxes.
>> > The server is behind a Linksys router and connected to a DSL modem 
>> > where
>> > they have their static IP address.  Everything on the Exchange 2000 
>> > side
>> of
>> > things is set up properly.  DNS is installed on it and (obviously,
> active
>> > directory is installed).  I have set things up according to both the
>> > Exchange server administrator's companion and the Windows 2000
>> administrator
>> > 's guide in terms of DNS, etc.  For the purpose of this post, I shall
> call
>> > this their "Exchange network".
>> >
>> >
>> >
>> > Right next to it is their "business network" which has one server and
>> > approximately 20 workstations.  This network is connected to a second
>> > Linksys router which, in turn, is connected to a cable modem.  The two
>> > routers have a single static route set up to each other and you can 
>> > ping
>> the
>> > IP addresses from either network.
>> >
>> >
>> >
>> > The sole server on the "business network" has DNS and Wins installed,
>> > however, it is not set up as a domain - it's a workgroup server whose
> name
>> > is "server.doman".  Likewise, all of the workstations on the business
> side
>> > of things which are running Windows 2000 professional are also part of 
>> > a
>> > workgroup.  There is no authentication or sign in mechanism and they 
>> > are
>> > fine by that.  The workstations are a hodge-podge of Office versions
>> ranging
>> > from office 98 to Office 2000.
>> >
>> >
>> >
>> > The problem is that when I try to connect to the Exchange server across
>> the
>> > static route from the business network, the name does not resolve.  I
> know
>> > that I could likely install Outlook 2000 on the business side of the
>> network
>> > which, I believe, lets you stick in the IP address of your Exchange
> server
>> > and stops trying to resolve the name (which is the problem I have with
> the
>> > Outlook 98 client), but that would be half-assed.
>> >
>> >
>> >
>> > What I want to accomplish with as little messing around with the
> business
>> > server (their consultant likes to blame anything that happens on their
>> > network on the fact that I went and stuck an Exchange server on the
>> network.
>> > . . fortunately, the VP of the phone company is an old Navy
> communications
>> > officer who knows that whatever I have done to their Exchange server
>> across
>> > a router is not screwing up their business network) is to get name
>> > resolution to happen across their router.  I tried putting a static DNS
>> > entry on both the DNS servers, but since the server on their business
>> > network does not have a fully qualified domain name, the only thing I
> have
>> > left to me is WINS, or so I think.
>> >
>> >
>> >
>> > The questions here are, first will the WINS server be able to broadcast
>> > across the router and, second, what do I set up in terms of WINS 
>> > servers
>> so
>> > that it resolves across these routers.  Ideally, I want to do as little
> as
>> > possible to both servers.  I could take a shortcut and open up an IMAP
>> port
>> > on their router so that the business side outlook clients connect to
> their
>> > Exchange server by way of going out to the web and then coming back to
>> their
>> > external DSL router -  but that's half assed and I want to set this
> thing
>> up
>> > right.
>> >
>> >
>> >
>> > Thanks in advance,
>> >
>> >
>> >
>> > Roger
>> >
>> >
>>
>>
>
>

Relevant Pages

  • Re: why have a server?...advice needed
    ... For 20-22 users and 30 machines, with a QUALIFIED IT Consultant, that amounts to about 5-12 hours per month of IT support and in my opinion, if the network is installed properly with little change other than adding a computer and a user periodically, there should be no real need for more. ... Had I charged them my full $150/hour rate, I believe they would have been billed a total of roughly $10,000 last year, and that includes an emergency rebuild/replacement of their server when the old hardware died. ... I don't know what the IT costs are or what the EXACT business needs you have are, but from what I'm understanding, I don't think the IT support costs should be more than what I stated above. ... At one of my clients, they are packed in like sardines and by redirecting their folders, they can sit at ANY unused computer and when they log on, they have complete access to all their files without having to do anything. ...
    (microsoft.public.windows.server.general)
  • OWA... Cant get it to work.
    ... Do you install iis together with the exchange server in ... with the Microsoft Outlook Web Access components that are ... Microsoft Exchange Server ...
    (microsoft.public.exchange.misc)
  • RE: Catchall not working, EXTERNALLY?
    ... Exchange server 2003 supports multiple clients, such as OWA, MAPI ... Microsoft CSS Online Newsgroup Support ... When I open the connection (over internet) to my exchange account, ...
    (microsoft.public.windows.server.sbs)
  • Re: seeking info on Microsofts spyware
    ... M$ servers can detect whether a computer on its network is ... >connecting including operating system, browser, browser versions, etc. ... >employees carrying out company business. ... >I have actually watched my machine call out to a microsoft server on my port monitor when searching for files. ...
    (comp.security.misc)
  • Re: using same workstation with SBS2000 and SBS2003 domains
    ... Thanks for using the SBS newsgroup! ... To make two SBS domains running in one physical network, ... to the following articles to setup VPN server and configure VPN client. ... Turn On and Configure Inbound VPN Access in Small Business ...
    (microsoft.public.windows.server.sbs)