Werbung: SecurityConsole.de verwaltet Ihre Computer mit Security Essentails aus der Cloud!
30 Tage kostenfrei testen und 20% Rabatt für Ihre Bestellung mit Promocode: WBF2685582
(Promocode gültig bis 31.12.2011)

Group:  English: Windows Server » microsoft.public.windows.server.networking
Thread: Server Access Problem on LAN

HTVi
TV Discussion Newsgroups

Server Access Problem on LAN
Somchai 12/27/2008 3:40:00 AM
First the setup of the system. We had one server which acted as a DC and also
run some web application. Now we have installed a new server (2008), demoted
the old one and made the new one as the DC, AD, DNS, File, DHCP and the old
one is only running the web application.

I have joined all workstations to the new domain which was no problem at
all. The problem however is that if I want to access the files on the server
(Network Place, Entire Network, MS Windows Network, XXX Server) I can see
the server name, however, I cannot connect to it. It says no permission!
However, strange enough, if I do a search for the IP of the server I can
connect no problem, no login screen or anything shows, just everything seems
normal. I can Map the drive and it works even after reboot, etc. Another
symtom is that I can ping the server from any workstation, however, I cannot
ping the workstations from the server. It very much sounds like a DNS
problem, however, nothing wrong I can see there. I cannot post a IPConfig as
I am not at the customers site however it is:
Server
IP Address 192.168.9.1
Subnet: 255.255.255.0
Gateway: 192.168.9.3 (Firewall)

Prim. DNS 192.168.9.1
Alter DNS 192.168.9.3

Workstations
IP Address 192.168.9.61.......
Subnet: 255.255.255.0
Gateway: 192.168.9.3 (Firewall)

Prim. DNS 192.168.9.1
Alter DNS 192.168.9.3

Windows Firewall is disabled and there is no third party firewall installed.
Anyone has any idea? It is driving me crazy.

Thanks to all you guys out there.
Re: Server Access Problem on LAN
"Bill Grant" <not.available[ at ]online> 12/27/2008 10:39:37 AM


"Somchai" <Somchai[ at ]discussions.microsoft.com> wrote in message
news:4225482F-B964-426E-A751-4DFCC01D3D6D[ at ]microsoft.com...
[Quoted Text]
> First the setup of the system. We had one server which acted as a DC and
> also
> run some web application. Now we have installed a new server (2008),
> demoted
> the old one and made the new one as the DC, AD, DNS, File, DHCP and the
> old
> one is only running the web application.
>
> I have joined all workstations to the new domain which was no problem at
> all. The problem however is that if I want to access the files on the
> server
> (Network Place, Entire Network, MS Windows Network, XXX Server) I can see
> the server name, however, I cannot connect to it. It says no permission!
> However, strange enough, if I do a search for the IP of the server I can
> connect no problem, no login screen or anything shows, just everything
> seems
> normal. I can Map the drive and it works even after reboot, etc. Another
> symtom is that I can ping the server from any workstation, however, I
> cannot
> ping the workstations from the server. It very much sounds like a DNS
> problem, however, nothing wrong I can see there. I cannot post a IPConfig
> as
> I am not at the customers site however it is:
> Server
> IP Address 192.168.9.1
> Subnet: 255.255.255.0
> Gateway: 192.168.9.3 (Firewall)
>
> Prim. DNS 192.168.9.1
> Alter DNS 192.168.9.3
>
> Workstations
> IP Address 192.168.9.61.......
> Subnet: 255.255.255.0
> Gateway: 192.168.9.3 (Firewall)
>
> Prim. DNS 192.168.9.1
> Alter DNS 192.168.9.3
>
> Windows Firewall is disabled and there is no third party firewall
> installed.
> Anyone has any idea? It is driving me crazy.
>
> Thanks to all you guys out there.

Have you joined this server to the new domain? The workstations will not
have permission to access its files if it is not a member of the new domain.

I would not list the firewall as an alternative DNS. It cannot resolve AD
resources. List the local DC only.

Re: Server Access Problem on LAN
Meinolf Weber [MVP-DS] <meiweb(nospam)[ at ]gmx.de> 12/28/2008 7:51:53 PM
Hello Somchai,

Is the old server member of the new domain?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


[Quoted Text]
> First the setup of the system. We had one server which acted as a DC
> and also run some web application. Now we have installed a new server
> (2008), demoted the old one and made the new one as the DC, AD, DNS,
> File, DHCP and the old one is only running the web application.
>
> I have joined all workstations to the new domain which was no problem
> at
> all. The problem however is that if I want to access the files on the
> server
> (Network Place, Entire Network, MS Windows Network, XXX Server) I can
> see
> the server name, however, I cannot connect to it. It says no
> permission!
> However, strange enough, if I do a search for the IP of the server I
> can
> connect no problem, no login screen or anything shows, just everything
> seems
> normal. I can Map the drive and it works even after reboot, etc.
> Another
> symtom is that I can ping the server from any workstation, however, I
> cannot
> ping the workstations from the server. It very much sounds like a DNS
> problem, however, nothing wrong I can see there. I cannot post a
> IPConfig as
> I am not at the customers site however it is:
> Server
> IP Address 192.168.9.1
> Subnet: 255.255.255.0
> Gateway: 192.168.9.3 (Firewall)
> Prim. DNS 192.168.9.1
> Alter DNS 192.168.9.3
> Workstations
> IP Address 192.168.9.61.......
> Subnet: 255.255.255.0
> Gateway: 192.168.9.3 (Firewall)
> Prim. DNS 192.168.9.1
> Alter DNS 192.168.9.3
> Windows Firewall is disabled and there is no third party firewall
> installed.
> Anyone has any idea? It is driving me crazy.
> Thanks to all you guys out there.
>

Re: Server Access Problem on LAN
Somchai 12/30/2008 1:47:01 AM
Yes it is.

"Meinolf Weber [MVP-DS]" wrote:

[Quoted Text]
> Hello Somchai,
>
> Is the old server member of the new domain?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > First the setup of the system. We had one server which acted as a DC
> > and also run some web application. Now we have installed a new server
> > (2008), demoted the old one and made the new one as the DC, AD, DNS,
> > File, DHCP and the old one is only running the web application.
> >
> > I have joined all workstations to the new domain which was no problem
> > at
> > all. The problem however is that if I want to access the files on the
> > server
> > (Network Place, Entire Network, MS Windows Network, XXX Server) I can
> > see
> > the server name, however, I cannot connect to it. It says no
> > permission!
> > However, strange enough, if I do a search for the IP of the server I
> > can
> > connect no problem, no login screen or anything shows, just everything
> > seems
> > normal. I can Map the drive and it works even after reboot, etc.
> > Another
> > symtom is that I can ping the server from any workstation, however, I
> > cannot
> > ping the workstations from the server. It very much sounds like a DNS
> > problem, however, nothing wrong I can see there. I cannot post a
> > IPConfig as
> > I am not at the customers site however it is:
> > Server
> > IP Address 192.168.9.1
> > Subnet: 255.255.255.0
> > Gateway: 192.168.9.3 (Firewall)
> > Prim. DNS 192.168.9.1
> > Alter DNS 192.168.9.3
> > Workstations
> > IP Address 192.168.9.61.......
> > Subnet: 255.255.255.0
> > Gateway: 192.168.9.3 (Firewall)
> > Prim. DNS 192.168.9.1
> > Alter DNS 192.168.9.3
> > Windows Firewall is disabled and there is no third party firewall
> > installed.
> > Anyone has any idea? It is driving me crazy.
> > Thanks to all you guys out there.
> >
>
>
>

Home | Search | Terms | Imprint Contact
Newsgroups Reader - provided by WiredBox.Net
Suche nach Orten, Städten, Postleitzahlen, Vorwahlen, Kfz-Kennzeichen