IP Office TFTP Server does not work on 200R2 Server

[RickKeifer]

We have now tried to get the tftp server to work through the voicemail server on 4 seperate 2008 R2 servers. When we point to the R2 server it just flat out doesnt work. we have completely disabled the firewall. The minute we put a copy of Manager on a different 2008 standard or below server it works perfectly. We are at a loss. We have may Small Business Server installs where we cant use the functionality.

 

[intrigrant]

Maybe the internal tftp server is active, it will block the manager tftp server.

Open up command prompt. Press "START" and "RUN" type "cmd" and use the command "netstat -a"
Look for port 69 or tftp

If it ain't dutch it ain't much

 

[hairlessupportmonkey]

have you tried a third party TFTP server like Solarwinds TFTP or Pumpkin TFTP.

You will soon get an error message saying the port is already in use. My as intrigrant has said, netstat -a on the offending server will reveal is port 69 is in use. Have you looked in the services (services.msc from a command line) and see if a windows TFTP server is already running?

ACSS - SME
General Geek

 

[RickKeifer]

I was really hoping this was it but i dont think so. Looked in services and no tftp of any kind either Microsoft or other.
The below is the spitout of my netstat. Dont see anything there. I would really like to get to the bottom of this and very surprised others havent hit this. We have tried on 4 differnt 2008 R2 servers with defualt brand new installs and no luck. The second we point to any other version it works.
==============================

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 CBO-Voicemail:0 LISTENING
TCP 0.0.0.0:143 CBO-Voicemail:0 LISTENING
TCP 0.0.0.0:445 CBO-Voicemail:0 LISTENING
TCP 0.0.0.0:3389 CBO-Voicemail:0 LISTENING
TCP 0.0.0.0:6002 CBO-Voicemail:0 LISTENING
TCP 0.0.0.0:7001 CBO-Voicemail:0 LISTENING
TCP 0.0.0.0:7002 CBO-Voicemail:0 LISTENING
TCP 0.0.0.0:8080 CBO-Voicemail:0 LISTENING
TCP 0.0.0.0:47001 CBO-Voicemail:0 LISTENING
TCP 0.0.0.0:49152 CBO-Voicemail:0 LISTENING
TCP 0.0.0.0:49153 CBO-Voicemail:0 LISTENING
TCP 0.0.0.0:49154 CBO-Voicemail:0 LISTENING
TCP 0.0.0.0:49177 CBO-Voicemail:0 LISTENING
TCP 0.0.0.0:49182 CBO-Voicemail:0 LISTENING
TCP 0.0.0.0:50791 CBO-Voicemail:0 LISTENING
TCP 127.0.0.1:42000 CBO-Voicemail:0 LISTENING
TCP 127.0.0.1:42001 CBO-Voicemail:0 LISTENING
TCP 172.20.1.135:135 cbo-monitor:3435 ESTABLISHED
TCP 172.20.1.135:135 cbo-monitor:3436 ESTABLISHED
TCP 172.20.1.135:139 CBO-Voicemail:0 LISTENING
TCP 172.20.1.135:445 cbostock-05:54208 ESTABLISHED
TCP 172.20.1.135:49154 cbo-monitor:2450 ESTABLISHED
TCP 172.20.1.135:49154 cbo-monitor:4141 ESTABLISHED
TCP 172.20.1.135:49200 172.20.1.47:12002 ESTABLISHED
TCP 172.20.1.135:50991 207.45.172.230:5721 ESTABLISHED
TCP [::]:135 CBO-Voicemail:0 LISTENING
TCP [::]:445 CBO-Voicemail:0 LISTENING
TCP [::]:3389 CBO-Voicemail:0 LISTENING
TCP [::]:47001 CBO-Voicemail:0 LISTENING
TCP [::]:49152 CBO-Voicemail:0 LISTENING
TCP [::]:49153 CBO-Voicemail:0 LISTENING
TCP [::]:49154 CBO-Voicemail:0 LISTENING
TCP [::]:49177 CBO-Voicemail:0 LISTENING
TCP [::]:49182 CBO-Voicemail:0 LISTENING
UDP 0.0.0.0:37 *:*
UDP 0.0.0.0:123 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5355 *:*
UDP 0.0.0.0:7001 *:*
UDP 0.0.0.0:42000 *:*
UDP 0.0.0.0:50791 *:*
UDP 0.0.0.0:52282 *:*
UDP 127.0.0.1:6001 *:*
UDP 127.0.0.1:53389 *:*
UDP 127.0.0.1:53390 *:*
UDP 127.0.0.1:62237 *:*
UDP 127.0.0.1:62239 *:*
UDP 172.20.1.135:137 *:*
UDP 172.20.1.135:138 *:*
UDP 172.20.1.135:6001 *:*
UDP [::]:123 *:*
UDP [::]:500 *:*
UDP [::]:4500 *:*

 

[hairlessupportmonkey]

Is the windows firewall enabled?

ACSS - SME
General Geek

 

[tlpeter]

By default the server 2008 blocks almost everything.

BAZINGA!

I'm not insane, my mother had me tested!

 

[hairlessupportmonkey]

indeed.

ACSS - SME
General Geek

 

[RickKeifer]

No the firewall service itself is completely disabled but I was thinking maybe something else may be blocking it. it is definitely something just cant put my finger on it.

 

[kwing112000]

a couple things come to mind. make sure the network discovery is set to private and not public and maybe make sure the folder sharing is turned on.

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries

 

[RickKeifer]

aha good ideas. i will try them and come back.

 

[RickKeifer]

it wont allow me to turn on network discovery i think because the firewall is disabled. i can re-enable the firewall but does anyone have the latest firewall settings (there is a command file out there i think that makes all the settings for you) so i can turn this thing on?

 

[hairlessupportmonkey]

Here you go

ACSS - SME
General Geek

 

[RickKeifer]

Thanks Again. i will try this and come back.

 

[eddiebullman]

Just out of interest what phones are you using ?

 

[tlpeter]

I am also curious about what ipoffice is used

BAZINGA!

I'm not insane, my mother had me tested!

 

[RickKeifer]

IT is only an issue with 9508 phones. All others come up with now issue. we did the inital upgrade remotely so not sure wether the other phones upgraded or not. There is a really good mix of 5400 series, 4400 series and even some really old 6400 series all of which are working great. Just the 9500's that are having the issues.

 

[eddiebullman]

I may be wrong on this but 1 think the 14xx and 95xx use HTTP not TFTP

Because I normally install manager on 2008r2 servers and point the default director of IIS service (WEB server) to the manager director

Which seems to work ok

But I am sure the other guys on here will tell me if I am wrong

 

[tlpeter]

Rick, what ipo on what software version?

BAZINGA!

I'm not insane, my mother had me tested!

 

[RickKeifer]

Hey guys im back and thanks for the input. Sadly I am still without a solution.
====================================================
First here are answers to some of the questions asked:
IP Office 500 V2 Console
IP Office Version on the 500 V2 is 10.1(43)
Phones I am trying to get to work are the digital 9508's
If I point the TFTP server to a 2003 machine running manager it works perfectly. New phones download software and boot no problem.
If i pint the TFTP server to a 2008 R2 machine (i have voicemail pro on it) it just sits at the Please Wait Screen
=====================================================
Here is what I have done
I have enabled the firewall service and ran the bat file to add all ports, etc.
I have verified physically that the firewall is allowing port 69 UDP for the tftp service
=====================================================
I am really at a loss here and it is getting worse now that 2008R2 is the standard!!!
When we deploy Small Business Servers we are sunk!!!

I found another interesting thing. When I run a netstat -a on the server 2003 computer i get:
UDP 172.20.1.38:69 *:*

On the Server 2008 R2 computer it is not listed at all.

It appears that maybe the tftp does not work on 2008 R2 even though everyone keeps saying it does or is there a reg setting, etc.

Any more ideas? I've tried everything!! I still stand a little mystified that nobody else has brought this up.

RK

 

[RickKeifer]

One correction to my previous post
The server it is working on is NOT server 2003 but Server 2008 Standard 32 bit
Dont know if that helps.

RK