IP500 install causes pc network problems 1

[peril0709]

Help! Upgraded from a 406 to a IP 500 last night.

We have an exchange network, with fixed IP addresses. When the IP500 is not plugged into the network all pc's can access the network correctly.

When we plug it in all but a handful experience a loss of connection to the network.

The DHCP settings on the IP500 are set to 'Dial in'

Does anyone have any ideas?

 

[TomMills]

what address does the IP office have? take the ip office off of the network and ping that adrress, see if something else has it.

Never argue with an idiot. bystanders won't be able to tell the difference.

 

[Maxwell1001]

diable DHCP and give the IP 500 a static which is free in that range..

have you got manager running on the network as well

ACA - IP Office
ACS - IP Office

 

[Maxwell1001]

just to make that clear, diable DHCP on lan 1 of the IP500 and give the IP 500 a static address which is free in your internal netwrok range

ACA - IP Office
ACS - IP Office

 

[peril0709]

The IP500 has a static address. Same as the 406 had.

Nothing else has the same address on the network.

Lan 1 The DHCP is set to Dial in.

Lan 2 DHCP is currently set to server but nothing is plugged into that port.

Manager is on the network with 4.2 (v11)

Thanks

 

[TomMills]

as maxwell said, disable dhcp on LAN1.

Never argue with an idiot. bystanders won't be able to tell the difference.

 

[peril0709]

Done as you suggested and taking the phone system down.

Now back up and re-booted one of the PC's - same problem.

 

[Maxwell1001]

1st reboot the pc, see if you get any IP conflicts etc..

let us know how you get on



ACA - IP Office
ACS - IP Office

 

[peril0709]

That's what I did. no network conflicts.

 

[Maxwell1001]

you said you have manage on PC's on the network....how many have the manager tool on them?

does this PC in question have it on?



ACA - IP Office
ACS - IP Office

 

[peril0709]

manager is only on a windows pc which acts as a voicemail server.

 

[amriddle01]

Did you use the 406 as a data switch at all? Some of those PC's may have the 406 as a gateway or something like that, so when the 500 fires up they are trying to route through that

ACS - IP Office Implement

"I'm just off to Hartlepool to buy some exploding trousers

 

[Maxwell1001]

thats that out the window then if you only have manager on the network once..

try giving the IP 500 a static that has never been used before and reboot...ping it before you assign it to ensure that its not in sue

ACA - IP Office
ACS - IP Office

 

[peril0709]

No the 406 was being used as a data switch.

Can't try renaming it now as I can't take the system down.

There is an error on the exchange server relating to the ip address of the voicemail pc. It won't allow dhcp to run as it thinks the vociemail pc is providing dhcp.

However, a) there is no dhcp coming from the voicemail pc, and b) everything has fixed ip addresses anyway.

 

[Maxwell1001]

try unticking enable bootp & tftp servers under file > preferences in manager.

then reboot voicemail machine ( as precaution) and problem pc in question...has an issue in the past with the TFTP on the manager..

obviously you need to try and set up some other type of TFTP server if this resolves this

ACA - IP Office
ACS - IP Office

 

[tlpeter]

Your server is probably a SBS2003 ?

If yes then it is a known problem

You need to change the registry on the sbs server

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCPServer\Parameters] "DisableRogueDetection"=dword:00000001

This will prevent the sbs server to responde on dhcp/bootp requists like it does

ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[Maxwell1001]

ah thats explains something, the fault i previously mentioned where we had issues and we disabled the TFTP server on the manager to fix it, well this was on sbs2003..

cheers for that was not aware this was a know issue

ACA - IP Office
ACS - IP Office

 

[peril0709]

Thought I would give you an update.

None of the solutions presented cured the problem.

In the end, a complete re-installation of windows xp professional was required on the client machines. The only thing the workstations had in common was the fact they were all connected to the network when the IP office was attached. The machines that were off, worked perfectly when they were re-booted.

Any chance that the effected workstations saw the IP office as a router, and consequently changed their local information in some way.

If we disconnect the IP office from the network the machines that have a problem connecting to the domain all work fine.