News:

Buffalo provides Data Recovery services. Read about it here.

Main Menu

2 Terastations causing trouble on Server

Started by DonARViox, January 22, 2009, 04:50:50 AM

Previous topic - Next topic

DonARViox

   

Hello guys,

i encountered the following errors on one of our servers.

 

Event Type: Error
Event Source: IAS
Event Category: None
Event ID: 13
Date: May 22, 2001
Time: 11:59:48 A.M.
User: N/A
Computer: Computername

Description:
A request was received from the invalid client IP Address IP_Address.

 

They come 4 at a time 2 from every ip of the two terastations. 

I did a little research for the error and amongst other things i found this article m$ 

http://support.microsoft.com/?scid=kb%3Ben-us%3B299684&x=11&y=18

 

According to the article it is caused by wrong setup of a Radius server BUT we dont use one.

And whats interesting about it is that the ips from the stations are reported...

 

Any suggestions, ideas?

Thanks in advance

 


DonARViox

   

Here some more info:

 

1st Station
terastation
firmware 1.04

2nd Station
TS-HTGL/R5 1.05
firmware 1.05

 

I still have no clue where thoses errors are coming from. 


classic

   i have the exact same error message! aldo no radius server installed... what is this?

DonARViox

   


could someone please look into this.

 

the problem still persists.

 

they both have one in common, the workgroup and the wins server.

does that matter in anyway? 

 

just give it a shot. 


Colin137

Sorry about the long wait for replies... This is quite a strange issue.

 

A few questions... what are the IP addresses and subnet masks of the two terastations? What is the range of IP addresses that your DHCP server provides to clients? What operating system is reporting the errors?

 

Also, it appears that you copy-pasted the error from the microsoft article. Could you post the error message as it appears in the event viewer?

Message Edited by Colin137 on 03-16-2009 09:26 PM

DonARViox

   

I am kind of disappointed for the lack of support.

But i will provide more information.

 

The IP Adresses of the two stations are 10.1.3.55 and 10.1.3.56 those adresses are excluded from the dhcp lease range. The operating system reporting is windows server 2000, our dns & dhcp server.

 

Event Type:    Error
Event Source:    IAS
Event Category:    None
Event ID:    13
Date:        19.03.2009
Time:        12:39:33
User:        N/A
Computer:    Servername
Description:
Von der ungültigen Client-IP-Adresse 10.1.3.56 wurde eine Anforderung empfangen.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

 here the ^^ original event. 


Colin137

The only thing I can find is perhaps the first case in that MS KB article: "The default path to the Remote Access log file has been changed or is not valid."

 

http://support.microsoft.com/?scid=kb%3Ben-us%3B299684&x=11&y=18

 

From the article:

Change or verify the path of the Routing and Remote Access log folder

               loadTOCNode(2, 'resolution');            The local System account must have write permission to the new folder. The default path is %systemroot%\System32\LogFiles.
  1. Start the Routing and Remote Access console.
  2. Right-click  Route Access Logging,  and then click Properties.
  3. Click the Local File tab.
  4. Change or verify the path of  the Routing and Remote Access log folder.

 


classic

   

Thank you Colin... it was not the fold of the diskstation... but the Routing & Ras of the questioned server was not enabled :D

 

 


Browser ID: smf (is_webkit)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 5: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default), StopForumSpam.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 242 (show)
Files included: 35 - 1354KB. (show)
Memory used: 1033KB.
Tokens: post-login.
Queries used: 16.

[Show Queries]