Manager R5 or R6 beta on Windows7 pro???

[jeffthephoneguy]

Does anyone have Manager working on Windows 7 pro? And if so how?

 

[BrantN]

Yes I have had 5 and 6 both running nothing special to installing them.

 

[jeffthephoneguy]

I keep gettting an error that says "network error - failed to communicate with IPOffice". I have unistalled and reinstalled both R5 and R6. I also changed the properties to XP SP3. Still the same error. It sucks I still have to carry my old laptop to work.

 

[BrantN]

Not sure if this might be IPV6 on the network properties but I had no problems with mine of course I am just using IPV4. As long as you are on the correct network which I assume you are there shouldn't be a problem. The test could be to install it in XP Mode and test it that way but I am assuming it is a network option or windows firewall problem.

 

[jeffthephoneguy]

I wish it was that easy... firewall is off right network, manager sees the system, but cannot connect.

 

[intrigrant]

If he manager "sees" the IP Office but it cannot continue then there is a problem with tftp.
Check whether port 69 is free on your pc and if you can use tftp, download free software like the 3COM tftp server and start it, if it cannot use port 69 you get a error notification.

 

[tlpeter]

Are you sure you have enough rights ?



ACSS - SME (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!

 

[hairlessupportmonkey]

turn off windows firewall.

 

[alexdykes]

I figured I would resurrect this thread since I am now having the same erorr with the R6 manager. I have disabled all forms of firewall and virus protection, but I still get the error network error - failed to communicate with IPOffice when I try and open the configuration on one of my IP412s. If I restart the VMPro server (the box the manager is installed on), then I can connect without issue for a day or so before it goes haywire again. I am running Windows Server 2003 Standard X86. Any ideas?

 

[Bas1234]

In windows 7 you more then 1 firewall check if the right one is turned off.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[kyle1532]

we had a proble like this with a system that had all IP phones. we found that the lan port was so busy we could not talk with the control unit. we could see it in manager...but when we put the password in to program we would get the same message.

we had to unplug the lan port...plug it back up...and then we could get in to it for the first couple of minutes. after that, when all the IP traffic started again...it was a crap shoot???

 

[element4749]

Just incase someone searched for this issue, the reason that you are getting "failed to connect to IP Office" even though you may be in the same subnet w/ firewalls off etc, is because of the amount of traffic like kyle1532 was suggesting.

In my case, I had one-X portal installed, which seemed to be taking up a ton of connections on that local host. Perform a netstat from the command line to see how many, if it begins to scroll endlessly off the screen that is most likly the case.

I uninstalled One-X portal and was able to connect right away, and my netstat showed very minimal traffic, which would appear normal.

Now, the question is, why would One-X Portal be causing so much traffic? Perhaps it would be best to keep it on a seperate server.

 

[tlpeter]

You could have just stopped the service
1XP needs status updates for every user that uses 1XP.
So that could be using some traffic but it will not prevent manager from finding the IP Office at all.

Put the IP address of the ipo in th field that has the broadcast address.

Then try again.


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.

 

[amriddle01]

Yeah, I think the cheapness of the IP Office LAN ports is starting to show again, have now had a couple of v2's where you can't see the system due to high traffic...only like 80-90 IP Phones and a couple of Soft Consoles. Became very hit and miss trying to get in with a few calls going

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

 

[element4749]

True I could have just stopped the service haha, but I am going to try to reinstall to see if it is going to generate the same amount of traffic from the get go.

It's very strange that it was spewing out so much traffic, this is a demo setup that I was working with, so very minimal users, one-X portal maybe had five users configured and I was still not able to connect.

Note that I could connect with Manager from another machine, just not from the Manager installed on the 1XP machine.

I always have the unicast address specified in Manager to connect.

I have never had a problem actually seeing the IP Office through Manager, just after typing the login/pass it would fail.

Strange.

 

[amriddle01]

Indeed, that's how it maifests itself, you see the unit in the connection window but you get that odd failed message when trying to get the config

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

 

[tlpeter]

I don't think it is because of cheap lan ports.
I think something goes wrong in the software.
Wasn't there a similar problem in 3.2 ???


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.

 

[amriddle01]

Possibly, it only happens when there is a fair load/higher traffic on the Lan port sometimes a reboot is needed to clear in my experiance

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

 

[tlpeter]

That is what happend in 3.2
The system could be seen but trying to pull a config gave a network error which was gone after a reboot of the system.


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.