Are these port scans of any importance?

Started by Steve, May 06, 2009, 21:09:17

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Steve

These are a frequent occurrence for me this evening

UDP Packet - Source:212.69.40.3 Destination:212.69.45.xxx - [PORT SCAN]
UDP Packet - Source:212.69.36.3 Destination:212.69.45.xxx - [PORT SCAN]
UDP Packet - Source:212.69.40.3 Destination:212.69.45.xxx - [PORT SCAN]
UDP Packet - Source:212.69.36.3 Destination:212.69.45.xxx - [PORT SCAN]
UDP Packet - Source:212.69.40.3 Destination:212.69.45.xxx - [PORT SCAN]
UDP Packet - Source:212.69.36.3 Destination:212.69.45.xxx - [PORT SCAN]
UDP Packet - Source:212.69.36.3 Destination:212.69.45.xxx - [PORT SCAN]
UDP Packet - Source:212.69.36.3 Destination:212.69.45.xxx - [PORT SCAN]

Are they of any importance? They appear to originate from the idnet DNS servers. I must admit my router DG834N DGTeam firmware is not enjoying them.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Steve

Anyone else having problems with idnet DNS this evening. I am spending a very long time  watching FF look ups?
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Steve

I think I've found the source of the problem I managed to screw up the whole of my network and internet connection by trying to upload a large file to the idisk@me.com which is also in sync with the desktop. I realized that that this was going to take a long time so canceled the upload as a result it seem to have been spending all evening trying to sync over the internet a non existent file between the desktop idisk sync copy and the web based idisk.

This resulted in the router logs showing dns port scans. as the by the time the request was made the return port had closed due to the high latency of my connection Ping times were in three figures on occasions. It was so easy at first to blame the DGTeam router firmware but a reflash to the original Netgear version did not solve the problem.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Simon

Sorry, can't help at all with that, Steve.  Are you sorted now?
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Steve

Yes I am sorted just spent a little time going round in circles try to source the problem. You can apportion blame to me or an Apple product. You decide. >:D
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Simon

Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Sebby


Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.