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

Hi Ace,

All clients on our network are XP Pro SP2, the Win2003 is SP1, all machines
are pointing to the internal DNS server with forwarder set to our external
ISP servers.

I will go through the link you sent me and see if any of the suggestions
posted there will help.

Makes sense that it could be some sort of timeout issue, but for it to
affect machines after a few seconds seems odd, you choose to sync then after
5 seconds or so it disconnects and states the win2003 is offline.

Thanks again.

kde


"Ace Fekay [MVP]" wrote:

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

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
Loading