Problem migrating to Windows Server2003 network

  • Thread starter Thread starter Justin Wallace
  • Start date Start date
J

Justin Wallace

I currently have a peer to peer network with approx 12 clients (all XP
pro). I recently purchased a server and windows server 2003. The
server setup went fine until I setup one of my clients which is
located in the engineering dept. They run some CAD software with uses
Flexlm to allocate a licence to each client. The licence server is a
service running on on one of the Xp clients. I keep getting an error
saying the licence host is not running or available yet I can ping the
client.
When I revert to the original network the licence server works fine.
I have noticed that I can telnet the port allocated to the licence
server also. I cannot do this when the client are logged onto the
Windows server. I am beginning to think that the server or client is
blocking access to the licences server, but I hav'nt a clue where to
start looking
 
I currently have a peer to peer network with approx 12 clients (all XP
pro). I recently purchased a server and windows server 2003. The
server setup went fine until I setup one of my clients which is
located in the engineering dept. They run some CAD software with uses
Flexlm to allocate a licence to each client. The licence server is a
service running on on one of the Xp clients. I keep getting an error
saying the licence host is not running or available yet I can ping the
client.
When I revert to the original network the licence server works fine.
I have noticed that I can telnet the port allocated to the licence
server also. I cannot do this when the client are logged onto the
Windows server. I am beginning to think that the server or client is
blocking access to the licences server, but I hav'nt a clue where to
start looking
Click to expand...

How is TCP/IP organized on your network? Static IP addresses or DHCP?
How do the Flexlm clients know where the licence server is? By etBIOS
name, IP address, or do they have their own discovery?

Could have something to do with Access Rights - make all Domain Users
members of the local machines' Administrators group:
NET LOCALGROUP ADMINISTRATORS "DOMAIN USERS" /ADD
(untested)

Could also have something to do with XP's firewall if you use SP2 -
disable it.
 
Back
Top