Windows Server 2003 Startup/Connection Problem

Hey Guys,

I was wondering if any of you out there could help me resolve this problem I am having on my server.

"At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details."

Sys Specs.
OS:Windows Server 2003 Small Business Server. Service Pack 2.
CPU: 3.40GHz
Memory:1GB

There seem to be a few warnings and one error under the application entry in event viewer.

Error reads like this:

Source:Microsoft ISA Server Con
Event ID: 14192

ISA Server Control Service Failed to Start because the operating system service Windows Firewall/Internet Connection Sharing (ICS) is already running. To fix this problem use ISA Server setup to reinstall ISA Server.

Do you really think it needs to be reinstalled?

And under System there are 2 errors:

Source: Service control Manager
Event ID:7024

Description:
The Microsoft ISA Server Control Service terminated with service-specific error 278540 (0x4400C).

Source: Service control Manager
Event ID:7023

Description:
The Windows Firewall/internet connection Sharing (ICS) service terminated with the following error:
The filename, directory name, or volume label syntax is incorrect.

Both of my internal/external network connections say they are connected and I can ping my external connections portal, 192.168.100.1, but when I try to access it via Internet Explorer to initialize my routers on the external connection to join a wireless network, it says page cannot be displayed.

My servers IP is 192.168.100.1
My portal is 192.168.100.1

Usually everytime I open IE it gives me a menu to choose which routers I would like to activate to then start searching for a wireless connection, which once connected gets shared through our internal network.

I hope this makes some kind of sense. =)

I look forward to any ideas/fixes you may have. Many thanks in advance.

DOA.

 

Are you running ISA server on that box? From what I see, you might have to disable ICS service on the server. Are you running NAT on that box before installing ISA? If you do, you might have to undo NAT services on your box and reinstall ISA again.

When you install ISA, you need to tell the software which NIC is public or private interface. ISA will do NAT for you.

 

Hi Merlin_72032,

Thanks for the reply.

I had a read around the web and so far most of the entries suggest that I need to reinstall ISA again in order to regain access to my server.

Seems like a web publishing rule has become corrupt.
I'm a bit of a beginner in server OS and networking. This could take a while if I'm not careful.

Related links to the following error codes if any of you seem to be struggling with the same problem.

Error: 7024.
http://support.microsoft.com/kb/837864/en-us

 

Sounds like that might be the issue. Except when using Windows as the NAT device, the internal network is 192.168.0.0/24. He doesn't have that listed on here, but definitely sounds like he has two different programs doing the same thing.

Dead0ralive, go to start > run > services.msc and disable windows firewall / ics in the menu and see if that fixes anything.

 

Yep, you are correct. ISA see both NICs as private network because they have 192.168.x.x range. He needs to specify which NIC is the public network and another one will be private. ISA will route the traffic for him.

I think he has remote-routing service turn on on his box. That why he has the error.

 

Sorry, I double post.