Re: New Win2003 Server always appears 'offline' to wireless users?



In news:043B48FD-8E3E-4497-97BF-E9965BBFE685@xxxxxxxxxxxxx,
kde <kde@xxxxxxxxxxxxxxxxxxxxxxxxx> stated, which I commented on below:
Hi Ace,

When the user shares were on the win2000 box there was/is no problem,
initially I have only moved one group (marketing) from the win2000
server to the bew win2003 server. When the status of the server
flips to offline I am still able to ping both servers by FQDN and IP
without any latency? All mapped shares to the new win2003 server
become inaccessible only the home folder is useable as it is set for
offline access.

If I change the group's setting back to point the profile, home
folder and login script for mapped shares back to the win2000 server
there are no issues users can see mapped shares and stay connected?!?

I have removed various users from the group into the users container
so that no restrictive policies are applied but still the same issue
occurs?

I haven't changed the security setting or group policies from the
win2000 server, the two servers use the AD Integration so all
settings have transferred over to the 2003 server from the 2000
server.

I will double check the security settings, but am really running out
of ideas, would the AD Integration be causing an issue?!? No doesn't
make sense because there's no problem when I change the users profile
back to point to the win2000 server?!? This issue is on the win2003
server but what's causing it is a real challenge to locate.

kde

What type of clients do you have? XP, 2000 or older? I know with older
clients (nt4 pre-SP4, Win9x and ME) have a security issue that needs to be
changed, but that's usually on a 2003 DC, but this is not a DC.

I assume the 2003 machine is SP1, which fixes some connectivity issues.

Also, I would like to assume, since your infrastructure is AD, that all
machines, meaning DCs, member servers and clients are ONLY using the
internal DNS server in their IP properties, and you probably h ave a
forwarder configured in DNS properties to forward any outside queries to
your ISP's DNS.

The reason I mentioned that is because I've seen numerous issues to the
point they can be detrimental, if you have an ISP's DNS in your machines' IP
properties. After all, just a reminder, AD stores service and resource
locations in DNS. When a client needs to authenticate or logon, it queries
DNS to ask which domain controller to use. If the ISP's is in there, it
maybe asking that guy, and he doesn't know anything about the internal
network.

Anyway, just wanted to mention that.

Read this thread, see if it applies:
http://www.computing.net/windows2003/wwwboard/forum/2534.html

Ace


.



Relevant Pages

  • Re: best way tO TRANSFER AD
    ... Would I install DNS on the new box as a secondary dns? ... Once I copy the reg key for shares will all shares automatically get ... > Then adjust the time server settings there as they are on your other ...
    (microsoft.public.windows.server.active_directory)
  • RE: How to Grant Power Users rights to administrative shares.
    ... This is on windows server 2003. ... right click shares and select new file share ... The "Create A Shared Folder Wizard" opens click next. ... Please check the permission settings of the shared folders. ...
    (microsoft.public.windows.server.sbs)
  • Re: Specified network name is no longer available
    ... Site C three laptops, no server.. ... Though strangely they can open up some shares from Site B! ... The DNS at Site A and B are obviously AD intergrated and are syncing ... much more data than the shares at Site B opens up just fine. ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN access to network file shares
    ... "The file shares are on a server running Windows Small Business Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Adding 2003 DC to 2000 domain...
    ... The new DC make also DNS server and reconfigure the domain machines to use it on the NIC as perferred. ... For the shares copy the data including permissions with robocopy form the old to the new machine and for the shares export and import ther registry key: ... If this computer is a domain controller for the specified domain, ...
    (microsoft.public.windows.server.setup)