Problems reaching server after inactivity

[markraves]

Hello,

In my company we have a windows 2003 sbs server. My problem is, that when a user comes to work in the morning, his / her computer can't reach the shares on the server. After a reboot, everything works normally. It used to work, but recently we changed isp, and I've set up a new firewall, since our new isp didn't have built in firewall in the equipment. I've moved the dhcp server to the new firewall, but run the dns server still as part of AD. WINS server service is still going on the 2003 sbs, and I've pointed the new firewall to give dns and wins ip of the server to the clients. But I have bo clue absolutely as to what happens after inactivity. Help appreciated!

 

[noveyron]

Would that be a reboot of the server or the client?

Is there anything in the event logs on the server of note?

What does an ipconfig /all show, both server and client?

 

[markraves]

Sorry for not providing enough info.
This is a reboot of the client.
I can use the internet, and I can access other newly booted workstations from the server and the unbooted client.

ipconfig /all on server:

IP 192.168.1.200
Mask 255.255.255.0
DHCP NO
GW 192.168.1.1
DNS 192.168.1.200
WINS 192.168.1.200
Primary DNS Suffix: MyComp.local
DNS Suffix Search MyComp.local
Node Type: Unknown
WINS Proxy Enabled: YES
IP Routing Enabled: YES

WS:

IP 192.168.1.21
Mask 255.255.255.0
DHCP NO
GW 192.168.1.1
DNS 192.168.1.200
WINS 192.168.1.200
Primary DNS Suffix: MyComp.local
DNS Suffix Search MyComp.local
Node Type: Hybrid
WINS Proxy Enabled: NO
IP Routing Enabled: NO

Event log has some info which I'n not familiar with:

The zone MyComp is configured to accept updates but the A record for the primary server in the zone's SOA record is not available on this DNS server. This may indicate a configuration problem. If the address of the primary server for the zone cannot be resolved DNS clients will be unable to locate a server to accept updates for this zone. This will cause DNS clients to be unable to perform DNS updates.

Maybe something here?
Thanks a bunch for replies.

\\mark

 

[gavm99]

Can the workstations ping the server when the problem occurs?

Gavin Moorhouse

http://www.lucidcomputersolutions.co.uk

Interested in my personal blog?

http://www.thelucidview.co.uk

 

[markraves]

Sorry for not posting, this is a remote branch, so I had to be here first;=)

The clients are logged into the domaincontroller in the morning. Now, the CRM program works. (it's installed locally, but keeps the database on the server.(Visma CRM)) But if you want to open an attachment or document via the crm, it locates it via path \\server\share\crm\attach\blablah\something.xls - and this share is not available.
I can ping everything, but doing a \\server or \\192.168.1.200 from explorer is not possible.

Thanks again,

\\mark

 

[markraves]

Hello chaps,

Forgot something..
To fix the problem (on a daily basis), a logout/login works. No reboot necessary.

Thanks,

\\mark

 

[markraves]

No hints to what I can do to fix this mess?
Thanks again,

\\mark

 

[mofusjtf]

Just a thought, but check the network card power settings on the workstations and the server. Make sure they are NOT set to turn off to save power.

 

[noveyron]

Also DHCP lease times.

I'm not sure the client DG is correct, it would normally point at the server?

 

[markraves]

Thanks,

Well,
Lease times isn't an issue, because it's static ip's on most computers, and they experience the same problems as the dhcp ones. And I've made sure that there's no overlap in dhcp range / static range.
I believe maybe this has got something to do with dns, but I've got no experience in dns management. Could this be?

Thanks again,

\\mark