Search results for query: *

Depends on the VPN Draytek do some very flexible devices - I've used the old 2600's and 2900's which can do IPSec quite well. Some of the newer ones have been slightly more buggy if multiple tunnels are employed but for simple stuff they'll be worth a look. They can do L2TP and PPTP dial in...

Sounds on first glance like an issue with encryption domains. If you allow all traffic through the vpn and it works then in principle all the other network settings are correct. You haven't said much about the VPN details but you'll need an encryption domain for each subnet which I assume is...

Guys - thanks - the relationship between route and COS/COR is something I have got to grips with pretty much. In answer to kwbMitel - that's the reason it came to my attention, we have no blocked numbers other than using COR, so I looked for 0898 etc in the ARS Table to copy and nothing was...

Hi Guys We've realised we have a problem with Premium rate call barring. Our extentions are set to disallow International and Premium rate calls - COR 4 - double checked by test calls. The issue is a particular prefix (rather not mention it) doesn't get blocked by this COR despite...

I wasn't aware it had to be a specific port - I don't remember it being an issue. From memory I recall it's easy to type the variables incorrectly expecially the filename - TFTPD32 is good for spotting that. Other than that it should work fine.

It's a quick and dirty fix - we use 255.255.252.0 subnets for certain large groups and they are appropriate in certain circumstances. The issues you'll have are: Any fixed devices will have the old mask and will not be able to "see" the new devices until altered - this will include your...

Having had a play - on the local netsh I can use interface ip add address "Local Area Connection" i.i.i.i m.m.m.m to add an address and then delete it but it seems those commands are not available to me in netsh -r - even going through manually. I suspect netsh is preventing it to stop loss of...

Well I thought so - but having had a quick try this end - I'm not so sure. The theory would be add the 224.216 address then use that 224.216 address as the -r machine to then remove the 224.200 - however I can't get those commands to work remotely - I'll have a quick fiddle...

I think a few more details would help. Can the users see the share but fail to open the mdb file or can they not even see the share? Have you checked connectivity to the server with a ping by name and IP address? On last thing - Access databases become notoriously unstable over slow links and...

I've used Netsh to change things like DNS settings but never been brave enough to try IP addresses. One tip - it would be sensible to add the new address as a secondary and establish connectivity on that address before removing the original. That may also give the RPC server something to hang...

If one works then it's unlikely to be the server config but please do post it anyway just in case - I agree it's likely to be connectivity to the ntp port on other Cisco routers. Now Windows clients are another matter - if I remember correctly you need to do some tweaks with the command line...

I would agree there is a slightly lower risk using a local admin rather than a domain level admin account. Should a virus be started under the Domain Admin account and tried to access network shares it will have more chance of infecting other machines it finds as it will automatically have...

Hmm. Network switches are HP's so will do VLAN's fine but can be fiddly without a management tool. We ahve a few left - you need to set ports on the web interface tagged into each vlan which can be confusing (and I've seen the Web interface fall over sometimes and had to go to command line)...

Apologies - missed that bit!

Oh - forgot to point out you could run both together then to allow you to migrate the older static devices at your leisure..

Oh yes indeed (assuming your Ip ranges are right) Just bear in mind because you've supernetted what looks like a class C address the odd device (ie printer cards some odd hardware like door controllers) might ignore the supernet. I've come across it most with cheap routers and printer cards...

Fair point. It's certainly slightly more complicated but it's usually the subnetting that bends the brain. DHCP will be tricky without vlans. One last thought is it's a lot easier to do it before you have too many devices.

DHCP should renew at half he lease time - when you are issued the ip what does the expiry say on ipconfig /all ? If it's 20 secs than that's correct behavour! The only other think is if the link keeps "micro-dropping" ie the card or the port sees a drop in the link layer it would renew. Look at...

Although there are advantages to using subnets on a flat layer two network it doesn't reduce much of the underlying chatter at layer 2 if you don't segregate into VLANs It's not clear whether you're segregating just for tidyness or for added security but deploying L2 VLANs along with subnetting...

Indeed - sometimes this can be that you have the device set for overlap when it should be set for en-bloc dialling. Occasionally it's a problem with older (non-ETSI kit) connecting to newer ISDN (ETSI Compliant) lines.