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 any of our Windows Server 2003 hosts with this IP. Windows Server 2008 Servers in the same subnet are no problem...
Does anybody know of such a problem? Mr. Google couldn't give me any satisfactory results... :-)
Cheers,
Mike
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 customers getting such addresses had troubles connecting to various services out there.
Mit freundlichen Grüssen
Benoit Panizzon
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. Windows 2008 has a lot of improvements in the IP stack, so I'm not surprised when it works now.
Beat
On Thu, Mar 31, 2011 at 9:44 AM, Mike Kellenberger < mike.kellenberger@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 any of our Windows Server 2003 hosts with this IP. Windows Server 2008 Servers in the same subnet are no problem...
Does anybody know of such a problem? Mr. Google couldn't give me any satisfactory results... :-)
Yes - Especially Windows machines seem to have a problem with .255 or .0, for that reason we have an exception in our DHCP-Daemon to exclude them.
Regards, Mario
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 this IP. Windows Server 2008 Servers in the same subnet are no problem...
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.
Regards Oli
We had a similar issue with a DSL.
We got also a .255 IP and we were able to bring up connections and also vpn's from and to the same AS, but we were unable to get any packet out of the backbone, also not with linux firewalls.
Finally we have changed the ip to .254
Regards Rene
Rene Hildenbrand HiHo GmbH Lochrütistr. 23 CH-8633 Wolfhausen
Mail:rene.hildenbrand@hiho.ch Web:http://hiho.ch Direkt: +41 (0)43 501 11 02 Tel: +41 (0)43 501 11 00 Fax:+41 (0)43 501 11 90 -----Ursprüngliche Nachricht----- Von: swinog-bounces@lists.swinog.ch [mailto:swinog-bounces@lists.swinog.ch] Im Auftrag von Oliver Schad Gesendet: Donnerstag, 31. März 2011 10:24 An: swinog@lists.swinog.ch Betreff: Re: [swinog] Connectivity problems with .255 IP Adress
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 this IP. Windows Server 2008 Servers in the same subnet are no problem...
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.
Regards Oli
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.
http://support.microsoft.com/kb/281579
Yes, time to upgrade :) (via google: "windows 2003 255 ip address") and then added "kb".
//Marcin
-
Beat Rubischon -
Benoit Panizzon -
Marcin Cieslak -
Mario Iseli -
Mike Kellenberger -
Oliver Schad -
Rene Hildenbrand