Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PhoneManager Lite issue with IBM Lap Tops?

Status
Not open for further replies.

IPOcpF

IS-IT--Management
Jul 16, 2007
9
CA
History:
AVAYA IP Office 412 Release 3.2(54)+ PhoneManger Lite 4.0 (18)

I haven't seen any posts on this yet.

My company uses IBM ThinkPad T-60 lap tops for the most part. I've got an issue with not being able to log in the PhoneManager Lite client into the call server... I can 'ping' the call server, but the PhoneManger can't locate the IP Office call Server?

More info, I don't have any problem with our IBM desktops, or other lap tops, only the IBM lap tops. Weird.

Also, our lan is set up in that the call server is in a different sub net then the clients, therefore we can't use the broadcast tool, we manually type in the static IP Office call server address, unicast works fine.

This is a strange issue, has anyone else had a problem like this, were you able to fix it?

Also, I actually use an IBM T-60 at work, and mine works fine! Again, weird.

Any info would be helpful. Thanks, cpF
 
You should be able to type the IP Address of the call server in the box and it should find it.

You may need to add a static route on the pc to point towards the correct subnet, although if you can ping it i would suggest you have a data path.



ACA - IP Office Implement
ACS - IP Office Implement
ACE - IP Office Implement
ACI - IP Office Implement
 
Thanks for the reply.

Yes, I know. I can replace the broadcast address (255.255.255.255) with the static IP Office Call server address (192.168.XXX.XXX) and press 'refresh'.

The problem is that with the IBM T-60 lap tops, it comes back with "could not locate server". With the desk tops,or our Toshiba lap tops, it finds the call server and I can log in.

Even when I can't 'locate' the call server, I can still 'ping' the call server.

???

I've ran the AVAYA port opening bat file as well, but it doesn't seem to make a difference.

We even took an IBM T-61 directly out of the box, before and company images were loaded, and loaded IP Office Phone Manager Lite - same issue.

I've turned off the local firewall as well, no difference.

I know the answer... don't buy any more IBM T Series laptops right? I wish I could just say that, but they're pretty standard issue, not my call.

???cpF
 
sorry if this does not help you much, but we deploy all T60s (at the moment) here and all the laptop users with Phone Manager work fine connecting to our demo system. I even killed the license server and PM Lite worked too.
I also tried one brand new out of the box, both PM and PM Lite worked prior to (base XP, no updates) and after imaging this with our standard image. Nothing else was done to these, plain default setups, not even the BAT file was run
Only difference I see with your dilema, is the label, ours are Lenova branded now
 
No, this is good. Maybe it's not only an IBM lap top issue. Although I can't figure out why everything else works.

One question... are you, jml2665, all on the same sub net, and using broadcast? I think that's the only other consideration with my application. cpF
 
If you type the IP address it should unicast and therefore travers the subnets as opposed to broadcasts which will be contained.

ACA - IP Office Implement
ACS - IP Office Implement
ACE - IP Office Implement
ACI - IP Office Implement
 
Check your network card is not set to some strange speed. i have had it when a VM server had a real strange speed set on the network card properties.

I would say ensure its Auto Detect or 10/100 Full Duplex.

Also what happens if your temp turn your firewall off on the machine.

ACA - IP Office Implement
ACA - IP Telephony
ACS - IP Office Implement (Aug 30th)
 
IPOcpf, yes on the same subnet and broadcast found the IPO without delay, I can't test on a separate subnet here, but if it helps one of our demo's was from a differnet office location on a different subnet and it worked fine a few weeks ago.
 
>AVAYA IP Office 412 Release 3.2(54)+ PhoneManger Lite 4.0 (18)

have you tried the correct version of Phone manager for your system?

Take Care

Matt
If at first you don't succeed, skydiving is not for you.
 
Yeah. The release of Phone Manager doesn't really make any difference. I've tried them all. I currently am using 4.0(18) on my IBM T-60, on a different sub net, and I don't have any issues, mine works fine. But I'm the phone guy...right?

I'll check the network card speed though on machines that aren't working. Mine's set to 'auto'.

PhoneManager doesn't contact the IP Office File Server, and you can't edit the network interface on the 412 Call Server.

cpF
 
Why would PM need tpo contact the file server(manager pc)?

You are pointing it to the IPO addresss aint ya?

ACA - IP Office Implement
ACS - IP Office Implement
ACE - IP Office Implement
ACI - IP Office Implement
 
Sorry, that's what I meant to say, that PM only needs to contact the IP Office Call Server, not the File Server.

I'll let you guys know if I solve the problem once I look into the network adaptor speeds. Thanks for all the feedback.cpF
 
I realize I am jumping in here late but, are you using a RIS image to install the laptops? Could just be an OS setting in the image which is making it seem common to the T60's.
 
OK. Here's the update. It has nothing to do with the IBM T-61 lap tops. I loaded PhoneManager n an 'out of the box' T-61 w/ Vista - and it works fine.

The trouble is with the XP Pro image our IT dept keeps loading on all new laptops.

If I find out what was happening with the image I'll let you guys know. Thanks, cpF
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top