menu

Showing posts with label Internet. Show all posts
Showing posts with label Internet. Show all posts

Monday, 29 December 2014

Why Comrade Cameron went all Russell Brand on the UK’s mobile networks

Analysis Dropped calls between President Obama to Prime Minister David Cameron on the Vodafone network over Christmas led to the government getting bossy with the mobile networks, according to industry sources.

The PM was in rural Oxfordshire over Christmas and decided that “something must be done” about rural mobile coverage. But the proposed cure is an odd one – closer to proposals floated by teenage socialist firebrand Owen Jones – to nationalise the country’s mobile infrastructure than a traditional incentive-based policy.

Mobile coverage reaches 98 per cent of the population – but around a fifth of the landmass is without a signal. Some of the operator’s own estimates put the cost of bridging the gap between £2bn and £4bn – and there aren’t enough people in those rural notspots to justify the investment.

No.10’s preferred solution isn’t better infrastructure, but giving consumers the ability to roam from network to network. The PM gave the plan to Maria Miller at the Ministry of Fun, who decided it was a rum idea. But after Miller resigned in April, her successor, ambitious business minister Sajid Javid, threw his weight behind the plan. Last night, a draft consultation went out to Britain’s big four: EE, Vodafone, Telefonica-owned O2 and Hutchinson’s 3.

The operators' objections to National Roaming broadly fall into three categories. It would create practical difficulties, they argue; it “contradicts 30 years of policy” (as one told me yesterday); and ultimately it will kill off long-term investment in rural infrastructure.

We all fall down

Leading the first set of issues is resilience: what happens when one network goes down – and everyone switches to another network? If rural mobile infrastructure is so poor that one network can’t cope with its own subscriber base – how well will it cope with two? And ultimately – with four? In the event of a single network failing, a domino effect is likely, operators say, as the entire rural subscriber base attaches at once. And this has serious repercussions, given the reliance of vital services on mobile coverage. Hence today’s briefings from the Home Office that National Roaming puts state security at risk.

There are other technical objections, too. Operators don’t support in-call handover between networks: so even a National Roaming experience is likely to be an unhappy one for the user if they’re on the move. And phones would need to be reprogrammed to search more aggressively for a higher priority network – every few minutes rather than 3GPP default of every hour – resulting in much faster battery drain. (See 3.2.2.5 in the spec

Who's calling us bumpkins?

Another pressing question is “what defines rural?” When the policy framework was established 25 years ago, lower frequency spectrum gave better coverage indoors. Today, high frequency spectrum is now used alongside it, so many users discover “notspots” in their own homes. If bumpkins can switch to another network, why can’t everyone else? Confining National Roaming to rural areas discriminates against the urban users who actually fund the network.

referensi : http://www.theregister.co.uk/2014/11/05/national_roaming_parklife/

Monday, 22 December 2014

Problem Connecting and Internet Network Solution


1. Network problems because of the failure of a network cable
Which is a common network problems we encountered due to the broken network cable that can affect the performance of a computer in the network because your patch cable cuts because bitten by rats; network problems that impact on a building block for inter-switch cable cuts (uplink cable); or even have an impact on most of the computers in your LAN network for backbone cable failure.


2. Network problems because of the failure of a network device
Scale disturbances result from the failure of a network device can also vary, from just a computer because of the failure of NIC - lan card; some computers because of the failure of a switch; or even a large scale because of the failure of the central switch that connects a network server. For failure lan cards in one computer can be replaced with a backup of your network card.

3. Network problems because of the failure of the system
The failure of the system could be because there is a problem with your DHCP server so that clients do not receive an IP address. Or it could be because there is a problem with your system so that clients Directory Services could not logon to jaringan.Atau could be due to a problem with the register name on your DNS system.

4. Network problems due to blast virus
This species is also a network problem that is not due to the failure of the physical network infrastructure, but the system will be overwhelmed with traffic your network of influence of viruses that attack and infect the server system to all computers in your network. The performance of your network system will be extremely slow even arguably collapsed. What can you do with this virus attack is to implement best practice security policy, you should be immune defense system once.

5. Connection Problems dashed
Cause: The quality of the telephone network decreases, telephone voice kemrosok or no hum
Solution: - Check the wiring of the house (from KTB up Modem)
- If you still try to report to the office nearest TELKOM

6. Slow Connection Problems
Cause: The number of shared PCs.
Activity Client-client PC Download or Upload Malware (Viruses, Trojans, Spyware) who spend your bandwidth Indeed Conditions Slow PC
Solution: Use Bandwidth management Use antivirus or anti spyware

7. The problem is on the Network Connection
  where the number of IP, Gateway dllnya nge-blank, but already in the manual settings, connected network status and still be able to access the data network via IPX / SPX / NetBIOS, but its IP number can not access the internet then stays off.
solution:
Error 1068: The dependency service or group failed to start. DHCP Client Service on Windows XP depends on the following three components: * AFD * NetBIOS over Tcpip * TCP / IP Protocol Driver If one of the above drivers fail the road, then the DHCP Client Service will fail way / not start.
Step I - Make sure that all three of the above driver files are in place Open Windows Explorer navigate to the folder% windir% \ System32 \ Drivers. Make sure the following files exist in the folder: * afd.sys * tcpip.sys * Netbt.sys
If one or more of the above missing files \ no, extrakkan from the Windows XP CD-ROM or from a folder ServicePackFiles \ i386. ---> What I do is unite from another computer that Windows XP it is still OK.
Step II - restarted Simple TCP / IP dah normal street and internet connection.


comment:
 
In a process that is on a computer network is not entirely due to provider error, but no human or human element itself is not careful in connecting to the Internet, for example:
1. Failure on the cable network bitten by rats
2. The number of users or clients that redundant data download
3. And the disruption of computer devices
We should be more careful.
 


Reference: http://www.ipanrock.info/2011/07/permasalahan-connecting-jaringan.html