Re: Problems when accessing server on other domain
- From: "Nils Magnus Englund" <nils.magnus.englund@xxxxxxxxx>
- Date: Fri, 29 Jul 2005 10:05:05 +0200
Hi Paul, thanks for your reply.
Perhaps I oversimplified the situation a little bit - I have three virtual
networks on the server, to simulate the DMZ, the LAN, and an additional
"secure zone". That's four connections for the firewall, including the
external network. We want to have a mini-simulation of our production
environment on the development servers, that's why we installed the
firewall.
However, I have tried to open for all traffic in the firewall (from any
source to any destination using any service is allowed), as well as using
the DNS server on the development network from my own computer (on the
external network) - none of which did much good. I still experience the same
problem.
Do you have any ideas on what makes it work for some servers, but not for
others?
Thanks.
Regards,
Nils Magnus Englund
"Paul Bergson" <pbergson@xxxxxxxxxxxxxxxxx> wrote in message
news:Or2yqZ3kFHA.3148@xxxxxxxxxxxxxxxxxxxxxxx
> The firewall probably doesn't have the proper holes opened or the servers
> don't have the dns setup to get to the test servers. It is probably dns
> though. Try putting the test dns server as a secondary on one of your
> servers that fails and see if this helps.
>
>
> If you are running NT in your production and AD in your test, I'm unclear
> as to why you would need a firewall between the two? There are no need for
> trusts etc... The two can run in harmony w/o the firewall.
>
> --
>
>
> Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
> "Nils Magnus Englund" <nils.magnus.englund@xxxxxxxxx> wrote in message
> news:OexaTc2kFHA.3544@xxxxxxxxxxxxxxxxxxxxxxx
>> Hello,
>>
>> We still use a NT4 domain on our production network. We recently bought a
>> server to use for development, on which we installed Microsoft Virtual
>> Server 2005 and a series of virtual servers. The virtual servers are
>> running on their own subnet, separated from our production network with a
>> virtual firewall (192.168.150.0/24 on our production network,
>> 192.168.250.0/24 on the development network).
>>
>> One of the virtual servers is the DC of our development domain (DEV),
>> running Windows Server 2003. The other virtual servers (all of which are
>> running Windows Server 2003) are members of this domain.
>>
>> The problem in question is regarding file sharing. My own computer is on
>> the production network, but I frequently need to access the virtual
>> servers on the development network. When accessing some of the virtual
>> servers (including the DC itself) by using e.g. \\server\c$ - I gain
>> access and can copy/modify/delete all I want (after supplying a valid DEV
>> domain login to the authentication dialog window).
>>
>> However, on other servers (at least two), I get the error "There are
>> currently no logon servers available to service the logon request.". I
>> have searched on it, but I couldn't find something I could apply to my
>> specific situation. I don't want the NT4 domain my own computer is a part
>> of, to be connected logically in any way to the development AD domain
>> (i.e. I don't want to set up any trust relationships etc. - the
>> development server should be wholly independent of our production
>> system). What causes this problem? Ideally, when accessing these servers,
>> I would want an authentication dialog box to pop up, as it did with the
>> other servers.
>>
>> Any tips, ideas and suggestions are welcomed!
>>
>> Thank you.
>>
>>
>> Sincerely,
>> Nils Magnus Englund
>>
>
>
.
- References:
- Problems when accessing server on other domain
- From: Nils Magnus Englund
- Re: Problems when accessing server on other domain
- From: Paul Bergson
- Problems when accessing server on other domain
- Prev by Date: RE: Dcpromo failed with "Directory object not found"
- Next by Date: RE: Slow user logon on Terminal server after migration to Windows 2003
- Previous by thread: Re: Problems when accessing server on other domain
- Next by thread: Allowed: Same name for forest and domain?
- Index(es):
Relevant Pages
|