Guys,
We are having a wierd issue here. Some subscribers are unable to log into MSN messenger or any microsoft websites (windows update, hotmail etc). They are bridged or natted, no difference.
Yet, when they use the same PC with a different ISP, they work fine.
What can i check as I am baffled…
I can work fine from our office.
Can they resolve the FQDN?
Can you bring a laptop there and hook up to their radio and have it work fine?
Is this an SSL issue? Maybe filtering/blocking 443 (for some odd reason) at your wireless router level?
Do these customers have somethnig in common such as a specific software firewall that could be filtering (for some reason) those domains? Just a stab…
The customers being affected are running save software version as each other? On the same AP as each other? Same subnet as each other? Etc…
They cannot ping the FQDN (though it resolves to the right IP) and the same PC will work with a different provider.
I can work fine from the office going through the same router and connection.
What is between the edge router and the customer that not between the edge router and you? Any switches, routers, DHCP servers?
Virus/Browser Hijack?
Had this happen once on one of our network segments, customer was infected and it seemed that they infected everyone in the same broadcast domain in a very short period of time.
Was able to easily prove that it was not our service by plugging a laptop into the same connection that was heavily shielded/protected from threats.
–SDH
Well, just as silently as it came… the problem disappeared.
Odd.
I ran into this problem once before - we have a /23 subnet (basically two Class Cs) and I was distributing them as such (x.x.x.x 255.255.254.0).
What would happen is the IP addresses in the middle that would normally be network and broadcast addresses (x.x.x.255 and x.x.x.0) were assigned to customers.
The Microsoft websites didn’t like that much and refused to accept connections. When I gave them a different IP the problem was gone.
So you were distributing the addresses with a /23 mask, and they were allocated to you as a /23? What is that, 510 usable addresses? Could you VLSM the /23 into two /24’s or is that what you are doing already? I guess it really all depends on where in the range of a netblock the addresses were allocated to you.
Just a comment on trying to ping sites such as www.microsoft.com and a lot of the ‘big boys’. Your ping will always timeout as their servers are set to not respond to ICMP request. You can have them do a tracert instead and they will get a response from all the routers along the route but the last hop will always timeout, verifying that they do have connectivity. I reserve using the ping command to a server in my office since I do not block the requests and have them do a tracert to any of the major sites outside of my network if connectivity is in question.
msmith wrote: So you were distributing the addresses with a /23 mask, and they were allocated to you as a /23? What is that, 510 usable addresses? Could you VLSM the /23 into two /24's or is that what you are doing already? I guess it really all depends on where in the range of a netblock the addresses were allocated to you.
Yes, they were allocated as a /23 per request. Worked out to be about 510 usable, yes. Basically the block is routed to another IP block of ours, then we distribute them as we see fit. We'll end up subnetting more down the road, but for the time being I'm still assigning them with the /23 netmask and just removed the troublesome addresses from the pool.
George_B,
Only problem I have with that is traceroutes, whether from one of my servers, routers or a route server from a global provider will always give false positives, how many switch fabrics have you hit to get 2-10 time outs before cancelling and not waiting for the absolute end result?
There are a few of the bigboys out there that still allow pings, google.com for instance or my favorite route-server.ip.att.net or time.nist.gov, by the way you can use the AT&T Route server to verify your routes and Announcements/Origination, etc.
I think it was Jerry that mentioned to not use pings for results, this is absolutely correct but for a down and dirty quick test pings to test Alive IP’s is beneficial but once you verify that ICMP requests respond, then you do have to goto the next step or steps, SNMP is good for this and layer 2 tests on your controlled network are better.
Wifiguy,
Out of curiosity how are you getting 510 usable IP’s out of a /23 in it’s entirety or even before subnetting. This would benefit me because if I can sqeek out those few extra’s ip’s I can almost eliminate half a class C :oops:.
–Shawn
We’re currently a (gasp) flat network - so I’ve simply got a DHCP server handing out the IPs. If you leave it as a /23, the usable IP range is x.x.1.1 - x.x.2.254, with x.x.1.0 being the network address and x.x.2.255 being the broadcast.
We’re slowly but surely getting out infrastructure straightened out and eventually (hopefully the next month or two, depending on when my ISP lights up my new backbone) it will be broken down into much smaller subnets, but for the time being it worked - we wanted to get our customers on public IP space instead of NAT.
I believe there are “workarounds” for utilizing network and broadcast addresses in smaller subnets, but I am not entirely sure how - I will definitely be experimenting when we start splitting up our network.
I have this same issue yesterday but later after trouble shooting the MSN messenger and repairing it, it works. But this is what i found in the event log:
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
00:03:36 UT : Mon Jan 01 2001 : File src/http_utils.c : Line 32 Reboot from Webpage.
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception – Watchdog Reset
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception –
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception –
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
00:00:49 UT : Mon Jan 01 2001 : File webportglu.c : Line 321 Sending page out to client return socket error 8: ECONNRESET
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception –
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception –
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
00:06:33 UT : Mon Jan 01 2001 : File webportglu.c : Line 321 Sending page out to client return socket error 8: ECONNRESET
00:07:19 UT : Mon Jan 01 2001 : File src/http_utils.c : Line 32 Reboot from Webpage.
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception – Watchdog Reset
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
17:01:14 UT : Tue Jul 10 2007 : File src/syslog.c : Line 1099 Time set
17:03:22 UT : Tue Jul 10 2007 : File src/http_utils.c : Line 32 Reboot from Webpage.
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception – Watchdog Reset
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
17:05:16 UT : Tue Jul 10 2007 : File src/syslog.c : Line 1099 Time set
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception –
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
17:21:02 UT : Tue Jul 10 2007 : File src/syslog.c : Line 1099 Time set
17:35:36 UT : Tue Jul 10 2007 : File webportglu.c : Line 321 Sending page out to client return socket error 8: ECONNRESET
17:36:25 UT : Tue Jul 10 2007 : File src/http_utils.c : Line 32 Reboot from Webpage.
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception – Watchdog Reset
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
17:38:16 UT : Tue Jul 10 2007 : File src/syslog.c : Line 1099 Time set
17:39:42 UT : Tue Jul 10 2007 : File webportglu.c : Line 321 Sending page out to client return socket error 8: ECONNRESET
17:40:47 UT : Tue Jul 10 2007 : File src/http_utils.c : Line 32 Reboot from Webpage.
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception – Watchdog Reset
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
17:42:36 UT : Tue Jul 10 2007 : File src/syslog.c : Line 1099 Time set
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception –
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
08:19:35 UT : Wed Jul 11 2007 : File src/syslog.c : Line 1099 Time set
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception –
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
00:08:40 UT : Mon Jan 01 2001 : File src/http_utils.c : Line 32 Reboot from Webpage.
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception – Watchdog Reset
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception –
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
00:07:17 UT : Mon Jan 01 2001 : File src/http_utils.c : Line 32 Reboot from Webpage.
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception – Watchdog Reset
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
00:02:01 UT : Mon Jan 01 2001 : File src/http_utils.c : Line 32 Reboot from Webpage.
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception – Watchdog Reset
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception –
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception –
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
12:13:00 UT : Fri Aug 31 2007 : File src/syslog.c : Line 1099 Time set
12:17:34 UT : Fri Aug 31 2007 : File webportglu.c : Line 339 Sending HTTP Header unsuccessful: -1: EPIPE
12:17:44 UT : Fri Aug 31 2007 : File webportglu.c : Line 339 Sending HTTP Header unsuccessful: -1: EPIPE
00:00:00 UT : Mon Jan 01 2001 : File src/syslog.c : Line 997 System Reset Exception –
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 409 System Startup
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 414 Software Version : CANOPY 8.1.4 SM-DES
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 418 Software Boot Version : CANOPYBOOT 1.0
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 424 FPGA Version : 102606
00:00:00 UT : Mon Jan 01 2001 : File src/root.c : Line 428 FPGA Features : DES Sched
15:59:21 UT : Fri Aug 31 2007 : File src/syslog.c : Line 1099 Time set
Please can some explain this to me,especially these
12:17:34 UT : Fri Aug 31 2007 : File webportglu.c : Line 339 Sending HTTP Header unsuccessful: -1: EPIPE
and
17:39:42 UT : Tue Jul 10 2007 : File webportglu.c : Line 321 Sending page out to client return socket error 8: ECONNRESET
Vanilla,
One thing you might want to do it this:
https://postmaster.live.com/snds/pref.aspx
If anything, it will tell you which IP’s Microsoft is blocking on your network. From what I understand this covers not only Hotmail, but MSN and the Microsoft sites as well.
I understand the aim of what you see makes you believe it is only for spam purposes but that is not correct.
When Microsoft Blacklists an IP or block of them they block any and all traffic, Port 80, 25, 443, etc.
By default there system will release it in 24-48 hours automagically unless there test Bots find the same exploit that caused them to automagically block it in the first place.
We had a problem about a month ago with a single customer. They could not open the hotmail.com or msn.com websites, and they would not accept that our laptop plugged into the same router at their house was the solution they were sold on it being a problem with our network, which was even more agitated by the fact that an hour before when they were still on dialup it worked, and after the install it did not.
I don’t know what Microsoft does when capturing this data, but the system was automatic and happened within 30 minutes, in the end the customer had something on their machine, we do not know the specifics because we were not allowed to touch it, but they did get it cleaned up and less than 2 days later everything worked.
When I called msn.com’s support desk, I was directed to network ops, they had me register on this system and bingo, I can see realtime which if any of my IP’s are blacklisted.
Hope this might be a useful tool in the future, especially if the propblem pops up again.
–Shawn
Cool thanks,
Took about 2 minutes to set up.
Awesome link, thanks…just signed up myself. =)