DNS issue?

[mingtmak]

I have a strange issue that I haven't been able to figure out the cause yet.

Initially setup SBS for a network w/o an existing domain or exchange server, SQL server, etc. They pretty much used just a file server.
When first setting up several issues arose...
- slow logins
- my document redirection not working
- unable to connect to default instance of SQL DB
- unable to add domain users to local admin groups of PCs joined to the domain (domain not showing up in 'location')

Initially setup in one location, then brought to new location for implementation...both gave same errors.
brought back to first location. Same issues.
Then isolated on a test network and all the issues went away. Placed back on the first network it was initially setup on and it still works. I had all PCs that were joined to the domain pointing their DNS to the SBS server.
I could ping the SBS server name and was able to join and log on to the domain.

It almost seems like a DNS issue, but not quite.
Has anyone experienced this before?

Right now it's all working as it should but I'd like to limit the possibility of this happening on the production network again. The network is fairly simplistic and I don't see other servers causing conflicts.

- Jon

 

[firthm]

Hi Jon,

Can you please give a very brief description of the network setup?

DNS Server - SBS?
DHCP Server - SBS?
DFG?
Able to ping domain.local?
Have you enabled SMB sigining on your client PC's?

I will post a link to an issue I once had which may be related after I send this. It caused similar symptoms as you've mentioned and was down to the fact that SBS has SMB signing turned on by default, and if your machines don't, they don't talk properly.

Thanks,
Mike

Michael Firth
Network Infrastructure Officer

~If it's not broke, break it and LEARN~

 

[firthm]

As promised:

http://www.tek-tips.com/viewthread.cfm?qid=1321034

Michael Firth
Network Infrastructure Officer

~If it's not broke, break it and LEARN~

 

[mingtmak]

Thanks, I will take a closer look at the article. Hopefully it gives me an idea of what was occurring. Here's some answers to your questions.

- DNS server was the SBS
- DHCP Server was the gateway router. Set the DNS IPs statically.
- DFG? (not sure what that is)
- can ping the server which domain sat on, never tried pinging "domain.local"
- SMB signing....unsure.

I had no trouble joining the domain or pinging the domain server. Which is why I found it odd that the other functionality wasn't working.
Also, since 'My documents' redirection wasn't working, I would have to set it once the clients joined the domain (subsequent logins at the same PC would keep the folder redirection). After which, when logging off, synchronizing would not occur. Though I could easily just go into the 'My documents' folder and shared drive it sat on at any point.
Even had a login script set at the domain server which ran successfully each time a client logged on to the domain.


- Jon

 

[firthm]

Hi Jon,

Sorry the DFG was default gateway and I assume this will be the same as your DHCP server.

If you get logon scripts etc OK it sounds as though you could be having group policy issues, do you receive "userenv" error messages in the event log on said PC's?

If you browse to \\yourdomainname.local\sysvol from one of the machines does it populate the sysvol share?

Sorry to fire questions!

Mike

Michael Firth
Network Infrastructure Officer

~If it's not broke, break it and LEARN~

 

[mingtmak]

No worries on the questions. I welcome them.

yes, DFG is the router serving the DHCP addresses.
I haven't noticed any userenv errors in event log. And since issue is not happening now, I can't reproduce it.

Yes, the sysvol share does populate at the moment.

What would this indicate if it didn't?
again, at present time it's working, not sure when I introduce it back to the new location if this will all work seemlessly.

- Jon

 

[Danny28]

In an SBS network, you should always disable any DHCP functions on your router. The SBS box must be the sole DHCP server. Your router should be the default gateway for your clients.

 

[mingtmak]

After implementing, the issue hasn't come up again. So still can't pinpoint where it went wrong the first time. I used all standard settings and setup steps. Oh well, it's working in production now normally.
It's still currently using the router DHCP, but that will change to the SBS server soon.

Thanks!

- Jon