Windows 2003 server -is part of a vlan but can't route

[blade10]

All-

I have built a Windows 2k3 server and added a static IP, subnet and GW based on a specific vlan given to me by the network admin.

It seems as though this subnet is not routable. when I do a print map from cmd, the table is not discovering any of the other routes/ip ranges...

I was told that you can enter a file with IP addresses that will allow routes to be open for this server? is that so? I don't exactly know how to type up this notepad file syntax wise or where to place it...

the windows firewall is "off" and other than asking the network team to open this address up or the security team to permit it through to other vlans and also the internet (which is important for outside access) I am down.

perhaps this "ip file" will help? anyone have any ideas on this particular option?

thanks

blade

 

[unclerico]

First things first, can you ping the default gateway?? Are you 100% sure that you entered the addressing info correctly??

In regards to the route print output, you should have a 0.0.0.0 route in the table with the outgoing interface addressed as your LAN interface; this is your default route. You can add a static route by opening a command prompt and enter route /? to see the syntax; however, it should not be needed.

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[blade10]

Hello Uncle Rico

It was a locked down vlan, although the vlan was established in had a guard on it, one IP per vlan...

Its all good now!

I have a external forest trust creation question for you.. will post it officially as a new entry in this forum ..

thanks so much

blade