Re: Applying Personal Settings



So are you thinking that the other workstations started acting up when you
changed out the switch? I wouldn't rule out that or another network
hardware issue at this point. If you re-run the CEICW, that should
eliminate any possible network configuration issues on the server (but not
ruling out the server NIC). It seems like between that and the server's
event logs, you should be able to rule out the server. Windows Server SP2
networking issues could be a factor except you're on SP1, right?

Running ipconfig /all on the workstations confirms that they're getting DHCP
from the SBS, not from a router or whatever?

I suppose you could try setting the NICs on the server and one of the
workstations to specific settings rather than auto-negotiate in case you've
got something going on with auto-negotiate. It does seem like if this were
a Dell NIC issue it would be more widely seen.

You don't have the AV on any server or workstation set to scan network
drives, right?

Does that server have a NIC diagnostic you can run?

"Robb Pierce" <RobbPierce@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:76E686D5-3FBB-4D8E-A661-49EF587855A2@xxxxxxxxxxxxxxxx
I have now found that 3 workstations on the network are doing this. these
others were not having this problem, but now seem to be. i've restarted
the
server a couple times, changed out the network switch, tested every single
cable. could this be a server related issue? I've turned all
workstations
off and a problem workstation turned on, still very slow logon.



"Robb Pierce" wrote:

thank you all for your replies, I put a cable tester on the line, tested
fine, all 8 pins. tried a different network card, still having the same
issues. thanx again for the help



"Robb Pierce" wrote:

New Server, sbs 2003 r2, sp1
existing xp clients, sp2

started setting up everything as i normally do for other clients, 2
nics in
server, 1 for lan, 1 for wan

all workstations on dhcp, with ipconfig results pointing gateway & dns
to
192.168.16.2, the servers ip address.

as i was adding clients to the network, everything was going great,
then i
found one computer that takes between 15-30 minutes to logon, holding
strong
on applying personal settings. i've double, triple checked dns
settings,
specified dns, still no luck. it feels like a dns issue, but i can't
see it
anywhere. went through msconfig, disabled all startup items, and
disabled
all services that were not microsoft, so nothing is running on the
machine,
still doing the same thing.

it would be extremely difficult to reformat this for the client, so i'm
hoping not to. the computer runs fast, except at logon, and also
doesn't
browse my network places, which confirms dns issues.

i'm looking for more than a basic answer of check dns, because static &
dynamic points to the servers lan ip, no wan info at all. i've
verified
ipconfig/all with other w/s and they match.

i feel hopeless, thanx.


.



Relevant Pages

  • Random Network Disconnects
    ... network and the only way I can seem to get it back up is to restart the box. ... Testing IpConfig - pinging the Secondary WINS server... ... DNS Host Name: itdspstest01.itd.edited.edited ... Provider Version:2 ...
    (microsoft.public.windows.server.dns)
  • RE: Server 2003 Network problems since IP address change
    ... Rightclick "My Computer", properties, Computer name or network identification, ... Is there any firewall running on client or server? ... Is the Primary DNS ... of zone WSW.local. ...
    (microsoft.public.windows.server.networking)
  • Re: About DNS naming convention for Active Directory
    ... Here's what I did so far, I set up a private network consists of the ... I did an in-place upgrade of the NT4 PDC to Active Directory 2003, ... I had no DNS service at all. ... Joined the 2003 Server as a member server and that went well too. ...
    (microsoft.public.windows.server.dns)
  • Re: Single NIC configuration with cable modem/router
    ... Internal or single network adapter configuration ... Verify the Domain Name System (DNS) pointers. ... Right-click Server Local Area Connection, ...
    (microsoft.public.windows.server.sbs)
  • RE: Strange Irregular DNS/Networking Problems
    ... My network is not a complicated set up and only has one domain controller. ... problems with DNS resolving after changing DNS servers. ... I was already using the server for DHCP. ...
    (microsoft.public.windows.server.dns)