Server Connection Issues 1

[simoncarter2003]

Hi guys,

Was wondering if any of you knew how to solve this. Recently setup a win server 2003 machine on my network. It is plugged into the router along with the clients on which they access the ineternet. As far as i know I have setup dhcp, dns and active directory on the server however none of the clients are able to connect to it. Nor does the server reply to pings, however can make ping requests itself. I have tried several methods to dish out ips including static, the router as the dhcp (windows dhcp disabled) and windows dhcp (router disabled). Neither of which have solved the problem of connecting to the server. However when running the windows dhcp an ip address was not obtainable from any of the clients. So it would appear as if there was only one-way traffic coming out of the server.
Any ideas?

Thanks simon

 

[simoncarter2003]

ok, for some reason it won't allow me to do an sp1 upgrade, it informs me that the upgrade is not possible at the present time. However i have got my hands on a crossover cable and connected the server direct to a client. Yet the server still blocks all incoming traffic. It refuses to allow clients to connect to it, and ignores all pings - none the less being able to ping the client. i really am stuck on this one. any ideas at all?

thanks simon.

 

[Loki1973]

Ok, at this point I'm suspecting a problem somewhere deep, deep inside the machine.

If nothing important is currently on the system, I would suggest a complete re-install. Is that an option?

 

[simoncarter2003]

Id prefer not. I wondered if you understood much about the service routing and remote access. I have had a few 'alert' messages pop up about this service, and was wondering what this service dont and whether it could be blocking incoming traffic?

thanks simon

 

[Loki1973]

RRAS could be very well be causing the problem, since it has firewall capability.

What are the errors you're getting?

Disable and unconfigure this service to start with and try pinging again.

 

[simoncarter2003]

Hi yeah that worked great. The ping now works, the dhcp client is providing ip's and the dns servers appear to be working fine. One last problem i appear to have is that when a client attempts to setup a connection to the doamin it informs you that it has found an account for the computer, but when you click yes it says the domain controller can not be contacted. any ideas before i start having a go?

thanks simon

 

[Loki1973]

Best should be to delete the Computer Accounts are re-add them to the domain just to be sure.

Glad I could be of help.

 

[simoncarter2003]

Tried that, deleted all computer accounts and re-added one of them. The client still gets the same error. But yea thanks for all your help, you've been great.

simon

 

[Loki1973]

Ok, tell me about the error:

* Which error exactly?
* What event is logged
* Where? At what point?

 

[Loki1973]

When you logon to the client locally, can you connect to the IPC$ of C$ share on the server? Does it prompt for a password?

 

[simoncarter2003]

thanks for all your help, ive fixed it now anyway so it doesn't matter. In the mean time you could point me in the right direction. I haven't really had much experience with windows servers and although i can quite easily (now) get users to logon to the server i was wondering how you get it so there desktop/background, potentially there home folder is also run trhough the server, rather than just mapping the home directory; instead of just the password being validated through the server.

thanks simon

 

[Loki1973]

This stuff can be configured for each user in their properties.