Hi
Does anybody know of such a problem? Mr. Google couldn't give me any
satisfactory results... :-)
This looks like a common misconfiguration on multiple 'router' or 'firewalls'
to filter such ip addresses.
We also had to exclude all .255 and .0 ip addresses from our dhcp ranges
because
Hi Mike!
On 31.03.11 09:44, Mike Kellenberger wrote:
One of our customers got a .255 IPv4 address assigned by sunrise.
he can't reach any of our Windows Server 2003 hosts
Sounds familiar. I had this problem with Windows 9x last time and
avoided the usage of .255 and .0 since those days.
On Thursday 31 March 2011 09:44:27 Mike Kellenberger wrote:
One of our customers got a .255 IPv4 address assigned by sunrise. I know
that this can be a valid host address with a netmask of /23 or greater,
but the strange thing is, that he can't reach any of our Windows Server
2003 hosts with
On Thu, Mar 31, 2011 at 9:44 AM, Mike Kellenberger
mike.kellenber...@escapenet.ch wrote:
Hi
Hi :)
One of our customers got a .255 IPv4 address assigned by sunrise. I know
that this can be a valid host address with a netmask of /23 or greater,
but the strange thing is, that he can't reach
On Thu, 31 Mar 2011, Oliver Schad wrote:
On Thursday 31 March 2011 09:44:27 Mike Kellenberger wrote:
Does anybody know of such a problem? Mr. Google couldn't give me any
satisfactory results... :-)
There is a old windows bug with .255, maybe it's still not solved.
5 matches
Mail list logo